Activity Monitoring, Tracking and Synchronization

ABSTRACT

A physical activity monitoring method and system may include a competition component requiring users to compete based on various metrics. The challenge may be device-specific, activity type-specific, user-type specific and the like. In some examples, the users&#39; performance might only affect the status of the competition if the user synchronizes the information to an activity monitoring system.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of U.S. application Ser. No.15/605,503, filed May 25, 2017, which is a continuation of U.S.application Ser. No. 14/186,425 filed Feb. 21, 2014, which claims thebenefit of and priority to U.S. provisional application Ser. No.61/768,279, filed Feb. 22, 2013. The content of the above notedapplications are hereby incorporated by reference in their entirety forany and all non-limiting purposes.

BACKGROUND

Exercise and fitness have become increasingly popular and the benefitsfrom such activities are well known. Various types of technology havebeen incorporated into fitness and other athletic activities. Forexample, a wide variety of portable electronic devices are available foruse in fitness activity such as MP3 or other audio players, radios,portable televisions, DVD players, or other video playing devices,watches, GPS systems, pedometers, mobile telephones, pagers, beepers,etc. Many fitness enthusiasts or athletes use one or more of thesedevices when exercising or training to keep them entertained, record andprovide performance data or to keep them in contact with others, etc.

Advances in technology have also provided more sophisticated athleticperformance monitoring systems. Athletic performance monitoring systemsenable easy and convenient monitoring of many physical or physiologicalcharacteristics associated with exercise and fitness activity, or otherathletic performances including, for example, speed and distance data,altitude data, GPS data, heart rate, pulse rate, blood pressure data,body temperature, steps taken etc. This data can be provided to a userthrough a portable electronic device carried by the user. For example,one athletic performance monitoring system may incorporate an audioplayer wherein data can be incorporated for display or furthercommunication on the audio player. Other systems may have a devicehaving its own display or the ability to display information on aseparate mobile device such as a smartphone. While athletic performancemonitoring systems according to the prior art provide a number ofadvantageous features, they nevertheless have certain limitations. Forexample, some users prefer not to use a portable audio player or preferto obtain and display performance data separately from an audio player.Other athletic performance monitoring systems have limited ability tofurther upload data to a personal computer or other location for furtherreview and consideration, or such data transfer is cumbersome for theuser. Still other systems can only monitor a single type of athleticactivity and cannot record the accumulation of various types of activityduring a day or predetermined time period. Other systems also do notoffer sufficient and creative feedback regarding the activity recordedand monitored.

A full discussion of the features and advantages of aspects of thepresent disclosure is referred to in the following detailed description,which proceeds with reference to the accompanying drawings.

SUMMARY

The following presents a general summary of aspects of the invention inorder to provide a basic understanding of at least some of its aspects.This summary is not an extensive overview of the invention. It is notintended to identify key or critical elements of the invention or todelineate the scope of the invention. The following summary merelypresents some concepts of the invention in a general form as a preludeto the more detailed description provided below.

Aspects described herein provide a system whereby competitions may bedefined between a plurality of users. The competition may be user,device and/or activity type specific. In other examples, the competitionmight only register a user's activity if the activity data issynchronized to a specified system, site, device, etc. In variousarrangements, a competition may require the user to achieve a specifiedamount of activity in a shortest amount of time. This may encourage auser to synchronize data as frequently as possible to win the challenge.In other examples, a challenge may require a user to achieve the mostamount of activity within a specified time period. This may alsoencourage the user to synchronize data as frequently as possible.

Other aspects and features are described throughout the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

To understand the present invention, it will now be described by way ofexample, with reference to the accompanying drawings in which:

FIG. 1 is a view of a person utilizing an athletic performancemonitoring and feedback system that in one exemplary embodiment of theinvention includes a wearable device assembly having athleticfunctionality;

FIG. 2 is a perspective view of the wearable device assembly shown inFIG. 1;

FIG. 2a is an alternative embodiment of the wearable device assembly;

FIG. 3 is a front view of the wearable device assembly shown in FIG. 2;

FIG. 4 is a side view of the wearable device assembly shown in FIG. 2;

FIG. 5 is a perspective view of the wearable device assembly shown inFIG. 2 wherein portions of the assembly are shown in transparent form toshow internal components;

FIG. 6 is a schematic cross-sectional view of the wearable deviceassembly taken along Lines 6-6 of FIG. 4;

FIG. 7a is a perspective view of battery compartments used in a spinemember of the wearable device assembly;

FIG. 7b is a perspective view of the battery compartments as part of thespine member;

FIG. 8a is a front perspective view of the spine member;

FIG. 8b is an underside perspective view of the spine member;

FIG. 9 is a perspective view of the spine member having a USB connectorattached;

FIGS. 10a-10c are views of the USB connector;

FIGS. 11a-f are views of a receiver member and other components for afastening mechanism used in the wearable device assembly and using theUSB connector;

FIGS. 12a-c are views of a spacer member or expansion element used inthe wearable device assembly;

FIG. 13 is a perspective view of the spacer member attached to thewearable device assembly;

FIG. 14 is a schematic plan view of a flexible circuit member of acontroller of the wearable device assembly described herein;

FIGS. 15 and 16 are perspective views of the spine member having certaincomponents of the device attached thereto;

FIG. 17 is an enlarged view of an input button associated with thecontroller;

FIG. 18 is a partial cross-sectional view of the input button of FIG.17;

FIG. 19 is a perspective view of the spine member having an outer memberformed thereon and showing battery compartments;

FIG. 19a is an underside perspective view of the device showing aportion of a battery compartment having a port opening;

FIG. 20 is a partial perspective view of a battery and closure memberand showing contacts of the battery;

FIGS. 21a-21d disclose various spine member and battery configurationsaccording to one or more aspects described herein;

FIG. 22 is an exploded perspective view of an alternative embodiment ofcontroller components of the device;

FIGS. 23a-c disclose additional views of controller components and adisplay and indicator system according to alternative embodiments of thedevice;

FIG. 24 is a partial exploded perspective view of an alternativeembodiment of a display and indicator system associated with thecontroller of the device;

FIG. 25a is a perspective view of a cap member used in the display shownin FIG. 24;

FIG. 25b is an underside view of the cap member shown in FIG. 24;

FIG. 26 is a partial cross-sectional view of the display of FIG. 24;

FIG. 27 is a partial enlarged cross-sectional view of a light member andcap member of the display of FIG. 24;

FIG. 28 is a partial exploded perspective view of components of analternative display of the device;

FIG. 29 is a partial exploded view of an alternative embodiment of adisplay of the device;

FIG. 30 is a partial cross-sectional view of a component of a latchmember incorporating a USB connector;

FIGS. 31a-33d are views of a latch mechanism of an alternativeembodiment of the device;

FIGS. 34a-34b are views of a spacer assembly of an alternativeembodiment of the device;

FIGS. 35a-37e are views of another alternative embodiment of a latchmechanism of the device;

FIGS. 38a-b are views of another alternative embodiment of a spacerassembly of the device;

FIGS. 39-42 are schematic views showing a process of forming the deviceof the present invention;

FIG. 43 is a schematic block diagram of the wearable device assembly;

FIG. 44 is a perspective view of the wearable device assembly pluggedinto a USB port of a computer;

FIG. 45 is an example process flow for an evaluation time period of awearable device assembly;

FIGS. 46 and 46 a are example process flows for an information displaymode of a wearable device assembly;

FIGS. 47A, 47B and 48-56 illustrate example user interfaces for awearable device assembly in an information display mode;

FIGS. 57A and 57B illustrate example battery indication interfaces for awearable device assembly;

FIGS. 58 and 58 a are example process flows for an action mode of awearable device assembly;

FIGS. 59A-59D, 60A-60D, 61A-61C, 62A, 62B, 63A-63D, 64 and 65 illustrateexample user interfaces for a wearable device in an action mode;

FIG. 66 illustrates an example process by which a location may bedetected;

FIGS. 67-71 illustrate additional example user interfaces for a wearabledevice assembly;

FIG. 72 illustrate an example process for configuring and registering awearable device assembly;

FIGS. 73A-73G illustrate example registration and configuration userinterfaces;

FIG. 74A illustrates another example process for configuring andregistering a wearable device assembly;

FIGS. 74B-74P illustrate example registration, configuration and setupinterfaces;

FIGS. 75 and 76 illustrate example messages indicating that the wearabledevice assembly is ready to be used;

FIG. 77 illustrates an example informational display for using thewearable device assembly;

FIGS. 78A-78G illustrate example interfaces for logging into andcustomizing an activity tracking application;

FIGS. 79-81 illustrate example interfaces for associating an activitytracking account with one or more social networking accounts;

FIGS. 82A and 82B illustrate example user profile interfaces;

FIG. 82C illustrates an example application mode selection interface;

FIG. 82D illustrates another example user profile interface;

FIGS. 83A-83H illustrate example user interfaces for tracking andvisualizing goal achievement progress;

FIGS. 84A-84F illustrate example notifications for tracking activitylevels and goals;

FIGS. 85A, 85B, 86, 87A and 87B illustrate example interfaces andinformation displays that may be provided upon the user completing aninitial evaluation period;

FIGS. 88A and 88B illustrate example interfaces for defining and/orsetting an activity goal;

FIGS. 89A-89D illustrate example interfaces for viewing current goalinformation and activity summaries;

FIGS. 90A-90C, 91-93, and 94A-94D illustrate additional example goalsetting interfaces;

FIGS. 95A-95C, 96A-96C, 97A-97C illustrate example progress trackinginterfaces including a progress bar;

FIGS. 98A-98C and 99 illustrate example streak tracking interfaces;

FIGS. 100A-100C illustrate example tagging interfaces for associatinginformation with recorded activity;

FIGS. 101, 102A, 102B, 103A and 103B illustrate example sharinginterfaces through which users may share activity information;

FIGS. 104A-104F, 105 and 105A-105D illustrate example activity summaryinterfaces;

FIGS. 106A, 106B, 107A-107E, 108A, 108B, 109A and 109B illustrateexample records, trophies and milestone interfaces;

FIGS. 110A and 110B illustrate example notification indicators;

FIG. 111 illustrate example activity notifications;

FIGS. 112A-112C, 113A-113C, 114A, 114B, 115 and 116 illustrate exampleachievements and accomplishment tracking interfaces;

FIG. 117 illustrates an example activity application setting menu;

FIGS. 118A-118C illustrate example activity application settinginterfaces;

FIGS. 119A, 119B, 120A-120C, 121A-121C, 122A-122C, 123A, and 123Billustrate example activity tracking interfaces that include activitytype tracking features;

FIGS. 124A-124C, 125A-125C, 126A-126C, 127A-127C, 128A-128C, 129A-129C,130A-130C, 131A-131C, 132A-132C, 133A-133C, 134A-134C illustrate exampleactivity summary interfaces including a breakdown of activity byactivity type;

FIGS. 135A-135D illustrate example interfaces for tracking activityalong with activity partners;

FIGS. 136A-136C illustrate example interfaces for comparing activity ofa user with others;

FIGS. 137A, 137B, 138A and 138B illustrate example activity competitioninterfaces;

FIGS. 139A, 139B, 140A and 140B illustrate example rewards andachievement notifications for user activity;

FIG. 141 illustrates an example interface displaying information fortracking progress toward a team oriented goal;

FIG. 142 illustrates an example notification for indicating the start ofa first goal period;

FIGS. 143 and 144 illustrate example application and device settinginterfaces;

FIG. 145 is a perspective view of an alternative embodiment of thewearable device assembly of the present invention;

FIG. 146a is side elevation view of a spine member having a PCB memberconnected thereto;

FIG. 146b is a perspective view of the spine member having plug membersattached thereto;

FIG. 146c is a plan view of the spine member having a PCB member andplug members attached thereto;

FIG. 146d is a plan view of the spine member and PCB member having plugmembers removed to expose adhesive members;

FIG. 146e is a partial perspective view of the spine member and PCBmember and having a flex clamp;

FIG. 146f is a plan view of the PCB member;

FIGS. 147a-147b are perspective views of plug members;

FIG. 148a is a partial perspective view of a first plug memberpositioned in a first flexible portion;

FIG. 148b is a partial perspective view of a second plug memberpositioned in a second flexible portion;

FIG. 149 is a side elevation view of the spine member having the PCBmember and plug members attached thereto;

FIG. 150 is a cross-sectional view of the wearable device assemblyshowing the plug members and outer encasement member;

FIG. 151 is a perspective view of an alternative embodiment of a USBconnector of the present invention;

FIG. 152 is a perspective view of USB leads of FIG. 151;

FIG. 153 is a partial perspective cross-sectional view of the USB leadsof FIG. 152;

FIG. 154 is a partial cross-sectional view of the USB connector of FIG.151;

FIG. 155 is an underside perspective view of the USB connector;

FIGS. 156a-156b are front and rear perspective views of a secondreceiver member of a fastening mechanism and a spacer member accordingto an alternative embodiment of the invention;

FIG. 157 is a perspective view of the second receiver member of FIGS.156a -156 b;

FIG. 158 is a side elevation view of the second receiver member of FIGS.156a -156 b;

FIG. 159 is an end elevation view of the second receiver member of FIGS.156a -156 b;

FIG. 160 is an end elevation view of the spacer member of FIGS. 156a-156 b;

FIG. 161 is a schematic perspective view of a second receiver member ofa fastening mechanism and a spacer member according to an alternativeembodiment of the invention;

FIG. 162 is a perspective view of the second receiver member of FIG.161;

FIG. 163 is a plan view of the second receiver member of FIG. 161;

FIG. 164 is an end view of the spacer member of FIG. 161 and having aspacer plate removed for clarity;

FIG. 165 is a perspective view of the spacer member of FIG. 161 andhaving a spacer plate removed for clarity;

FIG. 166 is a perspective view of an alternative embodiment of awearable device assembly having an alternative fastening mechanism;

FIG. 167 is a perspective view of a first projection member of thefastening mechanism shown in FIG. 166;

FIG. 168 is a rear perspective view of a second receiver member of thefastening mechanism shown in FIG. 166;

FIG. 169 is a rear elevation view of a second receiver member of thefastening mechanism shown in FIG. 166;

FIG. 170 is a perspective view of an alternative embodiment of awearable device assembly having an alternative fastening mechanism;

FIG. 171 is a perspective view of the alternative fastening mechanism ofFIG. 170

FIG. 172 is an exploded perspective view of the alternative fasteningmechanism of FIG. 171;

FIG. 173 is an end view of a second receiver member of the alternativefastening mechanism shown in FIGS. 170-172;

FIG. 174 is a perspective view of a wearable device assembly having analternative input button;

FIG. 175 is a perspective view of a spine member of the wearable deviceassembly of FIG. 174 and showing an actuation post of the input button;

FIG. 176 is a partial exploded perspective view of the input button;

FIG. 177 is a partial perspective view of components of the input buttonsupported by the spine member;

FIG. 178 is a partial cross-sectional view of the input button;

FIG. 179 illustrates an example physical activity competition interface;

FIGS. 180A-180C illustrate example user interfaces for synchronizinggame data and receiving status messages; and

FIGS. 181A-181F illustrate further examples user interfaces forsynchronizing game data.

DETAILED DESCRIPTION

In the following description of various example embodiments of theinvention, reference is made to the accompanying drawings, which form apart hereof, and in which are shown by way of illustration variousexample devices, systems, and environments in which aspects of theinvention may be practiced. It is to be understood that other specificarrangements of parts, example devices, systems, and environments may beutilized and structural and functional modifications may be made withoutdeparting from the scope of the present invention. Also, while the terms“top,” “bottom,” “front,” “back,” “side,” and the like may be used inthis specification to describe various example features and elements ofthe invention, these terms are used herein as a matter of convenience,e.g., based on the example orientations shown in the figures. Nothing inthis specification should be construed as requiring a specific threedimensional orientation of structures in order to fall within the scopeof this invention.

General Description of Aspects of the Invention

The present invention provides a wearable electronic device assemblyhaving athletic functionality. In one exemplary embodiment, the wearableelectronic athletic device assembly may comprise illuminable portionsthat convey athletic information to a wearer. Additionally, the wearableelectronic athletic device may include a data transmission portionconfigured to connect to (directly or indirectly) another device. In oneexample, the wearable electronic athletic device may include a USBconnector and storage device that may be connectable to a USB port ofanother device to transmit and receive data.

In one arrangement, the wearable electronic athletic device may includea USB storage device that may also be configured to act as a connectorto secure two ends of the wearable electronic athletic device assemblyto one another. The USB device is connected to a carrier that, in oneexemplary embodiment, is a wristband.

The electronic wearable device assembly may further include a housingportion that supports a controller therein. The controller hasassociated components such as a power supply and circuitry. Varioussensors may be operably associated with the controller including athree-axis accelerometer. The housing has a structural configurationwherein the housing is water-resistant as well as impact resistant.

In one or more arrangements, the controller may utilize a user interfacehaving certain features to enhance the functionality of the device. Forexample, the wearable electronic athletic device assembly may include adisplay that may include an indicator system wherein performance datacan be displayed or otherwise conveyed to the user. The display mayinclude an LCD screen, a display comprised of a series of LED lights, anLED graphical user interface and the like. The data displayed on thedisplay may be stored in an internal non-removable memory or a removableUSB storage device. Additionally, the USB device of the wearableelectronic athletic device may be plugged into a computer whereinperformance data can be automatically uploaded to a remote site ormobile device for further processing, display and review. The device mayalso be configured for the user to be prompted in order to commence adata transfer operation. The device may also be capable of generalwireless communication with other mobile devices or remote web sites.

In addition, the wearable athletic device may be worn in a variety oflocations on a user's body including on a user's chest (e.g., a cheststrap), around a user's wrist, around a user's arm, on a user's head, ona user's ankle or thigh, and the like.

In one exemplary embodiment, the display may include a display and anindicator system. The indicator system may display informationcorresponding to a level of activity of the user wearing the deviceassembly. The indicator system may include a plurality of light elementsthat are selectively illuminable to provide information. Each of theplurality of light elements may be illuminated in a plurality of colors.The display and indicator system may operate separately or in tandem todisplay indicia to the user.

In an additional exemplary embodiment, the device may include a spacermember that can adjust the size of the device to accommodate varioususers.

In still further exemplary embodiments, the device may interact withmobile devices and remote web sites to provide enhanced experiences tothe user.

SPECIFIC EXAMPLES OF THE INVENTION

While aspects of the invention generally have been described above, thefollowing detailed description, in conjunction with the Figures,provides even more detailed examples of athletic performance monitoringsystems and methods in accordance with examples of this invention. Thoseskilled in the art should understand, of course, that the followingdescription constitutes descriptions of examples of the invention andshould not be construed as limiting the invention in any way.

FIG. 1 generally discloses a person utilizing an athletic performancemonitoring and feedback system 1 that in one exemplary embodiment of theinvention includes a wearable device assembly 10 having athleticfunctionality. As explained in greater detail below, the wearable deviceassembly 10 has a sensor associated therewith such as a three-axisaccelerometer wherein the device 10 is capable of monitoring athleticactivity or overall activity of the user. As shown in FIG. 1, theathletic performance monitoring and feedback system 1 may also include afurther module or sensor 2, such as one carried by or embedded in ashoe, as well as a mobile device 3. It is understood that the system 1could also employ other types of sensors and devices if desiredincluding a heart-rate monitor. As discussed in greater detail below,various components of the system 1 including the wearable device 10 maywirelessly communicate with one another to record and monitor athleticperformance or overall user activity. It is further understood that theperson may utilize only the wearable device 10 to record and monitorathletic performance or overall activity. The athletic performance dataor overall activity can include a variety of different parameters,metrics or physiological characteristics including but not limited tospeed, distance, steps taken, and energy expenditure such as calories,heart rate and sweat detection. Such parameters may also be expressed interms of activity points (e.g., sometimes referred herein as “AP”) orcurrency earned by the user based on the activity of the user.

The shoe-based sensor 2 may have various electronic components includinga power supply, magnetic sensor element, microprocessor, memory,transmission system and other suitable electronic devices. The sensor 2in one exemplary embodiment is mounted on the shoe of a user as shown inFIG. 1. The sensor 2 is used in conjunction with the other components ofthe system to record data such as speed and distance among otherparameters of athletic performance. The sensor 2 can be a sensor asdisclosed in U.S. Publication Nos. 2007/0006489; 2007/0011919 and2007/0021269. These U.S. Publications are incorporated by reference andmade a part hereof. The sensor 2 could also take the form of aforce-sensor array to collect additional data associated with the user,such as disclosed in U.S. Publication Nos. 2010/0063778 and2010/0063779, which are incorporated by reference and made a parthereof. The mobile device may be a smartphone or other types of portabledisplay devices. The wearable device assembly 10 may also interact andcommunicate with other types of sensors including apparel based sensorsor sensors associated with events such as running competitions or otherathletic competitions.

FIGS. 2-6 illustrate different views of the wearable device assembly 10of FIG. 1. The wearable device assembly 10 generally includes a housing12, a controller 14, an input button 16, a display 18, and an indicatorsystem 20. It is understood that the controller 14 has and/or isoperably connected to various associated components including powersupplies, sensors and associated circuitry. FIG. 2a discloses analternative device 10 having a larger indicator system 20. The structureof the device 10 will first be described followed by a furtherdescription of the operation of the device and additional userexperiences provided by the device and related systems.

The housing 12 is in the form of a wearable band such as a wristband andgenerally includes an inner spine member 22 (FIGS. 6-9) havingcompartments for power supplies, an outer encasement member 24, and afastening mechanism 26 or latch member 26. In certain exemplaryembodiments, the housing 12 may have one or more spacer members 28 toadjust the size of the device 10 to be discussed in greater detailbelow.

As further shown in FIGS. 2-6, the wearable device assembly 10 isannular or generally circular in shape and, in this illustrativeexample, is configured for wearing around a user's wrist. The wearabledevice assembly 10 may be formed in various other shapes withoutdeparting from the invention, such as oval, oblong, octagonal,rectangular, and the like. The device 10 may also be configured to beattached to a clip or other device that can be removably attached to aperson, or incorporated into other apparel. The wearable device assembly10 and the housing 12 may include a generally planar portion and roundedor beveled edges along the sides. The beveled edge may only be includedon one side of the housing 12 in an exemplary embodiment. Ends of thehousing are configured to join with one another via the fasteningmechanism 26. In one or more arrangements, an outward or exterior facingside of housing 12 of the wearable device assembly 10 may include asmooth texture while an interior facing side (e.g., contacting thewearer's body) may include frictional features. In one example, theinterior facing side of the wearable device assembly 10 may be ribbed toimprove traction and prevent slippage around a user's wrist or otherbody part. The texture may be even throughout the interior side or maybe uneven. For example, the ribs or other texture may become morepronounced as the texture progresses away from the fastening mechanismformed at the ends of the housing. In other arrangements, texture mightalso be added to an exterior side of the wearable device assembly 14 andthe interior side may be smooth. Various combinations and configurationsof textures may be used. In still other embodiments, the housing 12 mayincorporate sweat absorption members on an inner diameter of the device10 or wicking elements.

As shown in FIGS. 7-9, the inner spine member 22 is a member havingsubstantially rigid portions and certain flexible portions or zones. Thespine member 22 generally supports components of the controller 14 asdescribed further herein. The spine member 22 may be considered achassis member having various components attached thereto. The spinemember 22 has a general curvilinear configuration and has an outersurface 30 and an inner surface 32. The spine member 22 has anintermediate portion 34 that extends to a first distal end 36 and asecond distal end 38. The intermediate portion 34 has a central portionor central segment 40 as well as a first segment 42 and a second segment44. The intermediate portion 34 further has a first flexible zone 46 ormember that connects one end of the central portion 40 to the firstsegment 42, and has a second flexible zone 48 or member that connectsthe other end of the central portion 40 to the second segment 44. Theflexible zones 46,48 provide for more easy flexing of the spine member22 at these zones and also the overall device while the first segment 42and second segment 44, and central portion 40, are considered rigidzones or substantially rigid zones. In an exemplary embodiment, theflexible zones 46,48 may be considered flexible hinge zones and arecurved segments in a generally concave shape. Thus, the flexible zoneshave a central portion or base portion with a pair of members extendingaway from the base portion, and therefore define an inwardly curvedportion. The curved segments have a thinned out thickness at the base orcentral portion of the concave configuration to enhance the flexiblecharacteristics of the flexible zones 46,48. Thus, the spine member 22has a general thickness or first thickness along its length (e.g., therigid central portion and rigid first and second segments) while theflexible zones have a lesser, second thickness “t” to assist in theflexible characteristics of the spine member 22 and overall housing 12.In particular, the base portion of the flexible zone has a lesserthickness than the rigid central portion and first and second rigidsegments. As explained in greater detail below, the flexible zones 46,48assist in the components supported by the spine member 22 to be closestto a neutral axis wherein stresses are minimized when the device 10 isflexed such as when placing on a user's wrist or removing the device 10from a user's wrist.

As shown in FIGS. 7-9, the first segment 42 of the intermediate portion34 has a first recessed compartment 50 and the second segment 44 of theintermediate portion 34 has a second recessed compartment 52. Thesesegments have a curvilinear configuration. The recessed compartments50,52 are dimensioned to receive power supplies associated with thecontroller 14. In an exemplary embodiment as shown in FIGS. 7a and 7b ,the recessed compartments 50,52 are initially formed from a metalenclosure such as a thixo-molded metal member 55. A thixo-molded memberis utilized in one exemplary embodiment while other members could alsobe used such as any cast metal members, die cast members or any metalinjected molded members. Metal cover or closure members in the form ofmetal caps are also provided as described below to provide a metalenclosure for the power supplies. It is desirable to form a metalenclosure for the battery or batteries 142 and it is understood that theenclosure may include confronting metal members that may not form acomplete chamber, but substantially surround the battery. It isunderstood that the thixo-molded compartments can be initially formedwherein the remaining portions of the spine member 22 are formed overthe thixo-molded compartments. Portions of the spine member may beformed over the thixo-molded members that define a bottom portion of thecompartments 50,52. The compartments 50,52 further have a pair ofopenings 59 to receive battery terminals or contacts to be described.The recessed compartments 50,52 may vary in size generally or withrespect to one another. Thus, the recessed compartments 50,52 may havean increased size to accommodate larger power supplies having increasedcapacity. Such features will be described in greater detail below.

The intermediate portion 34 further supports other components of thecontroller 14 proximate the outer surface 30 as well as the display 18and indicator system 20 as described further below. The spine member 22may have a beveled edge that supports the indicator system 20 thereon.The spine member 22 has certain openings to receive fastening mechanismssuch as adhesives and screw fasteners to fixedly attach controllercomponents to the spine member 22. The first distal end 36 and thesecond distal end 38 support the fastening mechanism 26 and optionalspacers 28.

In one exemplary embodiment, the thixo-molded members 55 that help formthe compartments 50,52 are made from magnesium wherein the remainingportion of the spine member 22 is made from a polypropylene materialthat is formed over the members 55. It is understood that othermaterials could be used for the spine member 22 as well as the batteryenclosures.

As shown in FIGS. 2, 3, 6 and 19, the outer encasement member 24 ispositioned around the spine member 22 and encases the controller 14, thedisplay 18 and the indicator system 20. In an exemplary embodiment, theouter encasement member 24 is a thermoplastic elastomer member that isformed in an injection molding process described in greater detailbelow. Accordingly, the outer casement member 24 has resilientelasticity while maintaining an annular shape. The outer encasementmember 24 has a generally rounded outer surface 56 and a generallyplanar inner surface 58, and may be considered to have an inner portiondefining an inner diameter of the device 10 and an outer portiondefining an outer diameter of the device 10. The outer surface 56 has asubstantially large radius to form a curvature while almost appearingplanar. The side edges have a smaller radius than the outer surface andthe beveled side edge further has a small radius. The surfaces of theouter encasement member 24 cooperate to form an internal volume to housethe various components of the device while maintaining a minimalcross-sectional dimension. The outer encasement member further has abeveled side edge 60. The indicator system 20 is positioned proximatethe beveled side edge 60. It is understood that the housing 12 couldhave beveled edges on each side edge if desired. The outer encasementmember 24 has an aperture 62 to accommodate the input button forinteraction with the controller 14. The outer encasement member 24 has afirst region 64 to accommodate viewing of the display 18 and a secondregion 66 to accommodate viewing of the indicator system 20. It isunderstood that the first region 64 is structured and dimensioned suchthat indicia projected by the display 18 can be viewed through the firstregion 64 of the outer encasement member 24. It is further understoodthat the second region 66 is structured and dimensioned such thatindicia projected by the indicator system 20 can be viewed through thesecond region 66 of the outer encasement member 24. The outer encasementmember 24 may include a colorant providing a dark appearance. The amountof colorant is controlled such that the components encased by the outerencasement member 24 cannot be seen. However, when the display 18 andindicator system 20 are activated, light easily projects through theouter encasement member 24 and is visually perceptible. For example, inone exemplary embodiment, the outer encasement member is translucentthermoplastic elastomer with a certain percentage of colorant. The outerencasement member 24 may further be considered generally transparent buthaving a tint provided by a certain amount of black pigmented material.In this configuration, the internal components within the outerencasement member 24 are generally not seen, however, when the display18 and/or indicator system 20 are activated, the light members areclearly seen through the outer encasement member 24. Thus, the internalcomponents are not seen via the naked eye, but the display and/orindicator system can be seen through the outer encasement member whenactivated. The device 10 may further be configured such that one of thedisplay and indictor system is always visible while the other one of thedisplay and indicator system is viewable only upon activation. Forexample, the display may always be viewable such as to show time of day,while the indicator system is only viewable when activated. It isfurther understood that the outer encasement member 24 may be a clearmaterial or include a variety of different colorants, or multiplecolorants. Certain colors may indicate a device 10 is specificallydesigned for certain types of uses or events. The first region 64 andthe second region 66 may be constructed to be transparent. In anexemplary embodiment, these regions are tinted to a darker color whereinthe display 18 and indicator system 20 are illuminated therethrough. Itis understood that alternatively, openings can be provided at the firstregion 64 and the second region 66 for viewing the display 18 andindicator system 20. The inner surface 58 of the outer encasement member24 has a first opening 68 and a second opening 70 proximate to thelocation of the power supplies supported by the spine member 22. Thefirst opening 68 is covered by a first cap 72 or closure member securedover the first opening 68 by fasteners, and the second opening 70 iscovered by a second cap 74 or closure member secured over the secondopening 70 by fasteners. The first cap 72 and the second cap 74 areformed from metal materials to cooperate with the metal batterycompartments 50,52 to provide a metal enclosure for the power suppliesto be described. The outer encasement member 24 may be composed of avariety of materials including a variety of polymers, plastics orrubbers, thermoplastic elastomer members, thermoplastic urethanemembers, liquid silicone members, and rubber composites, and othermoldable elastic members, and/or synthetics such as neoprene, plastics,textiles, metals and/or combinations thereof. In one or more examples,the material may include thermo polyurethane and/or thermoplasticrubber. The material used may also offer some flexibility so that thesize of the loop formed by the wearable device assembly 10 may beenlarged without fracturing or breaking the assembly 10. As explained ingreater detail below, an adhesion promoter may be used on the spinemember 22 and components supported thereon to assist in adhesion of theouter encasement member 24. The spine member 22 and outer casementmember 24 will be described in further detail below when describing theprocess of forming the device 10 below.

As shown in FIGS. 6 and 10-11, the fastening mechanism 26 or latchmember 26 generally includes a first projection member 90 and a secondreceiver member 92. The first projection member 90 is positionedproximate the first end of the housing 12, and the second receivermember 92 is positioned proximate the second end of the housing 12. Itis understood that the members 90,92 could be placed on opposite ends ofthe housing 12 if desired. The first projection member 90 incorporatesan input/output member 94 for data transfer and in an exemplaryembodiment, takes the form of a USB connector 94 having a substantiallyrigid body 96. The USB connector 94 includes a plurality of leads 98embedded in a top surface of the rigid body 96. The leads 98 haveconnectors that are operably connected to the controller 14. As shown inFIG. 10c , the first projection member 90 further has a recess 100positioned in a bottom surface of the rigid body 96 generally oppositeof the USB leads 98. The bottom recess 100 defines an engagement surface102.

As shown in FIGS. 6 and 11 a-f, the second receiver member 92 defines anopening 104 therein and supports a pivoting member 106. The pivotingmember 106 has a finger portion 108 and includes a spring 110 to biasthe finger portion 108 towards a latching position. The pivoting memberfurther includes a depressible button 112 to move the finger portion 108away from the latching position. The second receiver member 92 furtherhas a pair of prong members 120 at an opposite end from the opening 104.The prong member 120 has an inclined or curved cam surface 122. A slot124 is defined along the length of the prong member 120.

As further shown in FIGS. 11a-f , the first projection member 90 isreceived into the second receiver member 92 that may be connected to oneend of the spine member 22 in an embodiment. Initially, the fingerportion 108 is pivoted and biased away from the latching position. Oncethe finger portion 108 passes into the recess 100, the finger portion108 is biased by the spring 110 into the recess 100 and to the latchingposition. The device 10 is then in a closed position wherein the fingerportion 108 can abut the engagement surface 102 to maintain the device10 in a closed, annular configuration. While in an exemplary embodiment,the fastening mechanism 26 incorporates a traditional USB connector 94,it is understood that other types of connection configurations forcommunication could also be employed. For example, the device 10 mayutilize a micro USB connector, a Firewire port, a 16-pin pit, or othertype of physical contact-based connection, or may include a wireless orcontactless communication interface, such as an interface for Wi-Fi,Bluetooth, near-field communication, RFID, Bluetooth Low Energy, Zigbee,or other wireless communication technique, or an interface for infraredor other optical communication technique. It is further understood thatthe device 10 can be configured to communicate and data transfercompletely from a data transfer member such as the USB connector 94, orcompletely via wireless communication, or a combination of both wirelesscommunication and various types of plug-in communication.

FIGS. 10a-10c disclose additional views of the USB connector 94. The USBconnector 94 has structural features that provide a cleaner, moreaesthetically pleasing configuration while maintaining operability. Inconventional USB connectors, the leads are spaced apart unevenly, arerectangular in shape, and respective ends of the leads are not aligned.As shown in FIG. 10a , the leads 98 of the USB connector 94 are evenlyspaced a distance across the rigid body 96. In addition, the leads 98are recessed with respect to a top surface 114 of the rigid body 96. Inaddition, the rigid body 96 defines rounded openings 116 that are evenlyspaced and wherein the ends of the openings 116 are aligned. The leads98 are exposed by the openings 116. Because the leads 98 are recessedwith respect the top surface 114 of the rigid body 96, each lead 98 hasa raised rib 118 that extends proximate the top surface 114 of the rigidbody 96. In an exemplary embodiment, the leads 98 are placed in a moldwherein material is injection molded around the leads 98 to form therigid body having the uniform and aligned rounded openings 116. Suchstructure provides an enhanced USB connector 94.

The device 10 may be varied in circumferential size wherein the device10 can define smaller and larger loop configurations to accommodate, forexample, different wrist sizes of users. To this end, the housing 12 mayincorporate a spacer member 28 or expansion member or element 28 asshown in FIGS. 12-13. It is understood that a single spacer member 28may be used or multiple spacer members 28 may be used, or not used atall wherein the device 10 simply has the latch mechanism connected atends of the housing 12. The spacer member 28 cooperates with one end ofthe housing 12 and one end of the receiver member 92 of the fasteningmechanism 26 to increase the circumferential size of the device 10. Thespacer member 28 has a body 130 having one end having a pair of openings132 dimensioned to receive the pair of prong members 120 positioned onthe receiver member 92 of the fastening mechanism 26. The body 130supports a rotary pawl 134 proximate the openings 132. The rotary pawl134 has a curved cam surface 135 and has a biasing spring 136. Therotary pawl 134 is secured generally at a central location to the body130 by a fastener and cover plate shown in FIG. 12b . The rotary pawl134 generally is rotatable about the central location. The other end ofthe body 130 supports a pair of prong members 137 having cam surfaces138 similar to the prong members 120 of the receiver member 92. As canbe appreciated from FIGS. 11f and 13, when using the spacer member 28,the prong members 137 of the spacer member 28 are received in andsecured in openings in an end of the housing 12. This end of the housing12 has corresponding structure to receive such prong members 137. Theprong members 120 on the receiver member 92 of the fastening mechanism26 are inserted into the pair of openings 132 on the body 130 of thespacer member 28. To this end, the inclined cam surface 122 on thereceiver member 92 engages the cam surface 135 on the rotary pawl 134wherein the rotary pawl 134 rotates (Arrow A in FIG. 12c having coverplate removed for clarity) allowing further insertion of the prongs 120into the openings 132. Once the slots 124 on the prong members 120 alignwith the rotary pawl 134, ends of the rotary pawl 134 are received inthe slots 124 thereby securing the spacer member to the receiver member92 of the fastening mechanism 26 (See FIGS. 11f and 13). It isunderstood that access holes can be provided to rotate the rotary pawl134 when desiring to remove the spacer member 28 from the device 10. Itis understood that multiple spacer elements 28 may be used to increasesize or spacer elements 28 could be removed to decrease size. The lengthof the spacer members 28 may vary and in some cases, may range from 5-10mm. In one example, the length of the spacer elements 28 may be 8 mmeach. In another example, the length of spacer members 28 may be 6 mm.It is further understood that if an expansion element 28 is not used,the prong members 120 on the receiver member 92 cooperate with an end ofthe housing 12 to be secured thereto. In an exemplary embodiment, thespacer element 28 may have similar construction as the housing such as aplastic body having a thermoplastic member positioned over the body. Theprong member 120 may be part of a metal insert into the body. In certainexemplary embodiments, the inner diameters of devices 10 that mayutilize spacer members can vary from approximately 147 mm to 221 mm.

The device 10 has the controller 14 that is supported by the housing 12.The controller 14 generally includes a printed circuit board 140 havingvarious components including circuitry, processing units, data storagememory, connectors and other known components as understood in the art(FIG. 43). The controller 14 further includes a power supply 142 in theform of a battery pack(s) or batteries 142, an antenna assembly 144 anda sensor assembly 146. The controller 14 could also have othercomponents such as a speaker for conveying audible information. FIG. 43discloses a block diagram of the controller showing additionalcomponents associated therewith and will be described in greater detailbelow.

FIG. 14 shows a schematic view of the printed circuit board (PCB member)140. In an exemplary embodiment, the PCB member 140 is a flexiblecircuit member. The PCB member has various regions or sections tosupport the various components thereon. The PCB member further has acentral region 140 a wherein the display 18 and indicator system 20 areoperably connected thereto. The PCB member also has flex regions 140 bthat will correspond in position to the flexible zones 46,48 of thespine member 22. Other components described herein are also connected tothe PCB member 140. As shown in FIGS. 15 and 16, the PCB member 140 iswrapped around and mounted to the spine member 22. Fasteners may be usedto fixedly attach the PCB member to the spine member 22. It isunderstood that the central region 140 a of the PCB member correspondsto the central portion 34 of the spine member 22 when connected. The PCBmember 140 generally follows the contours of the spine member 22including the contours of the flexible zones 46,48. Thus, the flexregions 140 b are positioned at the flexible zones 46,48 of the spinemember 22 and in general surface-to-surface engagement. Thisconfiguration allows the PCB member to be moved proximate a neutral axiswherein stress on the PCB member is minimized when the device 10 isflexed.

As discussed, the PCB member 140 supports the various components of thecontroller 14. For example, the PCB member 140 supports the antennaassembly 144 and the sensor assembly 146. The PCB member furthersupports data storage memory components. Data storage memory receivesinput from the sensor assembly and as well as receives inputs from theUSB connector 94. Data stored by the controller 14 can also betransferred via the USB connector 94 to another device such as acomputer and also to a remote site via the computer (FIG. 44).

The antenna assembly 144 supported by the PCB member 140 assists incommunication with other mobile devices. Thus, the device 10 is capableof wirelessly communicating with mobile devices, and in one exemplaryembodiment, the controller 14 utilizes Blue tooth wirelesscommunication. The controller 14 may, therefore, have a Bluetooth radioand utilizes the antenna assembly 144 wherein the device 10 maywirelessly communicate with a mobile device. It is understood the device10 is equipped with other necessary components for such wirelesscommunication. Further examples of such communication will be describedin greater detail below.

As discussed, the PCB member 140 supports a sensor assembly 146 thereon.The sensor assembly 146 may comprise a plurality of different sensors.In an exemplary embodiment, the sensor assembly 146 comprises anaccelerometer in the form of a three-axis accelerometer. As explained ingreater detail, the sensor 146 detects movement corresponding toactivity of the user wearing the device 10. It is understood that thesystem 1 and/or controller 14 may also include other sensors as desired.For example, the system 1 utilized by the user may utilize shoe-basedsensors that communicate with the device 10. The user may also haveapparel based sensors that can communicate with the device 10. It isfurther understood that the sensor assembly 146 could include a heartrate sensor. The heart rate sensor could be chest mounted sensor ifdesired. It is understood that the heart rate sensor could also beincorporated into the housing 12 of the device 10 such as a sensor thatdetects heart rate proximate a wrist of the user. Other sensors couldalso be utilized such as GPS sensors. Additional sensors may also beincorporated into the device 10. In one exemplary embodiment, the sensormay include a gyroscope sensor. The sensor may be amicroelectromechanical system (MEMS) type gyroscope device. Such asensor may cooperate with other sensors in the device such as theaccelerometer to provide enhanced functionality and capabilities as wellto provide further differentiation of sensed movements of the user.

As discussed, the controller 14 includes the power supply 142 in theform of batteries 142. It is understood that a single battery 142 couldbe utilized in the design. Such a design may allow for a flexiblecircuit member having additional areas to support additional componentsassociated with the device 10. In an exemplary embodiment, however, thepower supply 142 utilizes a pair of batteries 142. As can be appreciatedfrom FIGS. 6 and 20, the batteries 142 have a curvilinear or curvedconfiguration and are generally rigid members. The batteries 142 definecurved planar surfaces. In an exemplary embodiment, the device 10utilizes the pair of batteries 142. The first battery 142 is positionedin the first recessed compartment 50 of the spine member 22, and thesecond battery 142 is positioned in the second recessed compartment 52of the spine member 22. The batteries 142 have a thickness thatgenerally corresponds to a depth of the recesses 50,52. The batteries142 are generally flush with the inner surface 32 of the spine member22. It is understood that the batteries 142 are operably connected tothe controller 14 to provide power to the device 10. As shown in FIG.20, the batteries 142 have a resilient boot member 148 associatedtherewith. The boot member 148 has a pair of rounded protrusions 149 andbattery contacts 150 of the batteries 142 are adhered over the roundprotrusions 149. The batteries are positioned in the recessedcompartments 50,52 wherein the contacts 150 extend through the openings59 in the compartments 50,52 and engage the PCB member 140 to providepower to the device 10. When the caps 70,74 are fastened down on thespine member 22, the round protrusions 149 and contacts 150 areresiliently pinched against the PCB member 140 providing an enhancedconductive connection. It is understood that each battery 142 utilizes aresilient boot member 148. In additional exemplary embodiments, aconductive epoxy member may be used to join the battery contacts. Theoverall size of the batteries 142 and respective recessed compartments50,52 may vary such being larger to increase battery capacity and lifeof the device before requiring recharging. It is appreciated that therigid batteries 142 are mounted in the more rigid first segment 42 andrigid second segment 44 of the spine member 22. The flexible zones 46,48of the spine member 22 allow the segments 42,44 and batteries 142 tohingedly pivot about the flexible zones 46,48 to provide a generallyflexible housing 12 and device 10.

As shown in FIGS. 2-6 and 16-19, the device 10 includes a depressibleinput button 16 assist in operation of the device 10. As can beappreciated from FIGS. 17 and 18, the input button 16 is operablyconnected to the controller 14 and supported by the housing 12 generallyadjacent the display 18. The input button 16 is accessible to the uservia the input button 16 extending past the outer encasement member 24 ofthe housing 12. The input button 16 has a rigid base member 76 and aflexible cap 78 integrally formed together in a two-shot moldingprocess. An internal chamber 79 is defined by the input button 16 tosupport a tact switch that can interact with the controller 14. Therigid base member 76 has an upper ring 80 defining a first tool surface82 and a lower ring 84 adjacent the flexible cap 78 and defining asecond tool surface 86. During the process of forming the device 10, thefirst tool surface 82 and the second tool surface 86 engage a tool intight surface-to-surface engagement when the outer encasement member 24is injection molded around the spine member 22 and supported components.This engagement prevents the injection molded material from flowing intothe internal chamber 79 of the input button 16 which would prevent theinput button 16 from operating correctly. Operation of the device 10from inputs provided via the input button 16 will be described ingreater detail below.

As shown in FIGS. 2 and 15 and 16, the display system 18 or display 18of the device 10 is supported by the housing 12 and operably connectedto the controller 14. The display may be considered an illuminableportion of the device 10 or housing 12. The display system 18 mayinclude a series of individual lighting elements or light members suchas LED lights 152 in an exemplary embodiment. The LED lights may beformed in an array and operably connected to the PCB member 140 at thecentral location. The LED lights 152 may be arranged such that words,letters, numbers, symbols and the like may be produced by lightingvarious combinations of the individual discrete LED lights 152. Forexample, LED lights 152 may be arranged in a matrix formation having aspecified number of rows and columns. The outer encasement member 24 ofthe housing 12 surrounds and protects the LED lights 152. As discussed,the outer encasement member 24 has the first region 64 (FIG. 19) andcorresponds to the locations of the LED lights 152 so that once the LEDlights are illuminated, the light is visible through outer encasementmember 24 (in an alternative embodiment, the first region 64 could bemade transparent or substantially transparent). It is understood thatthe first region may be individual and discrete. For example, each ofthe illumination regions may be surrounded by non-transparent or opaqueportions of the outer encasement member 24 such that illumination fromeach of the LED lights 152 does not blend together. The display system18 may span only a portion of the total circumference of the wearabledevice assembly 10. For example, as illustrated in FIG. 2, the displaysystem 18 occupies a top portion or central portion of the device 10opposite the fastening mechanism 26. The size of the display system 18(e.g., the number of individual LED lights, number of rows and columnsof lights, an overall width or length) may be determined based on amaximum amount of data to be displayed at any one time, a size of thefont and/or characters to be used and/or combinations thereof. In oneexample, the display system 18 may be composed of 5 rows of 20 LEDlights 152, wherein each row is substantially parallel to the length ofwearable device assembly 10. Additionally or alternatively, the overallexterior circumference (e.g., of an outward facing surface of the deviceassembly 14) may range from 174-182 mm. It is also understood that thedisplay 18 could include a light member indicating the device 10 iscommunicating via wireless connection such as Bluetooth communicationwith a mobile device.

As also shown in FIGS. 2 and 15 and 16, the indicator system 20 of thedevice 10 is supported by the housing 12 and operably connected to thecontroller 14. The indicator system 20 may also be considered a portionor component of the overall display 18. The display system of the device10 may be considered to have a first display and a second display. It isunderstood that the indicator system 20 can operate and illuminate inconjunction with the display 18 or completely separate from the display18. The indicator system 20 may also include a plurality of additionallighting elements 160 or light members 160, which may also take the formof LED lights in an exemplary embodiment. The light members 160 areoperably connected to the controller 14 and supported by the PCB member140. The indicator system 20 is positioned generally at the side edge ofthe housing 12. In one particular example, the indicator system 20 mayinclude a series of twenty lighting elements 160. Optionally, lightingelements 41 may run along both side edges of the housing 12 of thewearable device assembly 10. The lighting elements 160 are alsopositioned in a generally linear configuration in an exemplaryembodiment. The lighting elements 160 of the indicator system 20 may bedifferently shaped from lights 152 of the display system 18. Thedifference in shape, size or other appearance attribute may allow a userto identify the type of information being conveyed. The lightingelements 160 may, for example, line one or more of the beveled sideedges 60 of the housing 12 of the wearable device assembly 10, allowingfor ease of viewing by the user. In the example where the sides or edgesof wearable device assembly 14 are rounded, the lighting elements 160may be positioned on an outer curvature of the rounded edges such thatlight may be seen when worn (e.g., facing away from the user's wrist orother body part on which the device 14 is worn). Similar to theconfiguration of lights 152 of the display 18, the outer encasementmember 24 has the second region 66 (FIG. 19) that is at locationscorresponding to the position of lighting elements 160 of the indicatorsystem 20. Light projected from the light members of the indicatorsystem 20 are viewable through the outer encasement member 24 at thesecond region 66 (in alternative embodiments, the second region 64 couldbe transparent or substantially transparent). In one or morearrangements, the appearance of illumination produced by lightingelements 160 may be defined by the size, shape, transparency and otherappearance attributes of a corresponding portion of the outer encasementmember 24. For example, the lighting elements 160 might actually becircular (e.g., circular bulbs) but may be used to illuminatetransparent rectangular regions of the outer encasement member 24,thereby producing rectangular indicators (See e.g., FIG. 2a ). Theplurality of lights 160 of the indicator system 20 may extend around aportion of the circumference of device assembly 10. In one example, theplurality of lights 160 of the indicator system 20 extend generally thesame length of the length of the display 18. Spacing between the variousplurality of lights of the indicator system 20 and display 18 may alsobe similar. In another example, the light members 160 may extend aroundapproximately half of the circumference while in other examples,indicators light members 160 may extend around approximately a third ofthe circumference. In yet another example, the light members 160 mayextend around three-quarters or substantially the entire circumferenceof the wearable device assembly 10. It is also understood that theplurality of lights 160 comprising the indicator system may be groupedtogether wherein the indicator system may have different segments. Thedifferent segments of the indicator system 20 may be illuminated indifferent configurations as described in greater detail below. Eachlighting element 160 may also be considered a separate individualsegment of the display. From the configuration of the display 18 andindicator system 20, it is understood that the display 18 may projectlight in a first direction, and the indicator system 20 may projectlight in a second direction 20, wherein the first direction is differentfrom the second direction. In one exemplary embodiment, the seconddirection may be generally transverse to the first direction. It is alsounderstood that the light members of the displays could take othervarious forms and structures that provide illuminable characteristics.

FIGS. 39-42 are schematic views illustrating a molding process forcreating a wearable device assembly according to aspects of theinvention. In FIG. 39, a first mold 170 may be used to create the spinemember 22 of the wearable device assembly 10. As discussed, thestructural features of the spine member 22 allow the attachment,insertion and mating of various electronic and non-electronic componentsof the wearable device assembly 10. The spine member 22 may be moldedfrom a plastic material such as a thermoplastic material injected intothe mold 170. The spine member 22 may be thinner in some portions suchas the flexible zones to provide flexibility in those regions. Incontrast, other portions such as the segments supporting the batteriesmay be thicker to provide more rigidity. In addition, the electroniccomponents such as circuits and lighting elements (e.g., LEDs) may beattached to more rigid portions to prevent breakage. Subsequently, thespine member 22 may be assembled with other components as describedabove. For example, the battery packs 142, circuits, display 18 andindicator system 20 may be assembled with the spine member 22.

As further shown in FIG. 40, the assembled spine member 22 supportingcertain of the various components may then be wrapped or loaded onto aninsert core 172 for further injection molding. An interior diameter, orinner portion, may then be injection molded onto the spine member 22. InFIGS. 41 and 42, the molded assembly may then be inserted into an outerdiameter mold 174 and an outer diameter, or outer portion, of thewearable device assembly 10 may be molded to completely form the outerencasement member 24 of the housing 12. The device assembly 10 can thenbe removed from the insert core 172.

It is understood that additional processes can be utilized in formingthe device such as the device 10 shown in FIGS. 1-6. In an exemplaryembodiment, a process of forming the spine member 22 initially includesforming the battery compartments. As can be appreciated from FIGS. 7a,7b, 8a and 8b , a mold is provided wherein via a thixo-molding process,magnesium is injected into the mold to form the thixo-molded members 55.The magnesium thixo-molded members 55 cooperate with the metal batterycaps 70,74 (FIG. 2) to provide a substantially metal enclosure for thebatteries 142. As discussed, other metal forming processes can be used.Once formed, the thixo-molded members 55 are placed in a mold whereinmaterial is injected into the mold to form the spine member 22. Thematerial is overmolded around the thixo-molded members 55 wherein acertain amount of injected material extends over an internal surface ofthe members 55 (FIGS. 7-8). It is understood that the mold is designedto incorporate forms for the substantially rigid portions of the spinemember 22, the flexible zones 46,48 of the spine member 22 as well asother structures for receiving, mounting or otherwise supporting thevarious components of the device 10 as described herein. In an exemplaryembodiment, the material injected over the thixo-molded members 55 toform the remaining portions of the spine member 22 is polypropylene.

Once the spine member 22 is formed, additional components are connectedto the spine member 22. For example, one end of the spine member 22 canbe connected with connection structure that will cooperate with eitherone of the latch mechanism or a spacer element. It is further understoodthat the USB connector 94 is formed having the features described above.As can be appreciated from FIGS. 10a-10c , the USB leads 98 are providedhaving the raised ribs 118 formed such as through a stamping process.The leads 98 are placed in a mold wherein plastic injection moldedmaterial is formed around the leads 98 to form the rigid body 96 aroundthe leads 98. It is understood that the mold is designed such that therounded openings 116 are formed and wherein the leads 98 are then spacedapart equally and vertically aligned. While the leads 98 are recessed inthe rounded openings, the raised ribs 118 extend to proximate a topsurface 114 of the rigid body 96. The mold is also designed to form therecess 100 in the rigid body 96 of the USB connector 94. Once formed theUSB connector 94 is connected to an end of the spine member 22 whileends of the leads will be ready to be connected to the controller (FIG.9).

The spine member 22 with the attached components may then be insertedinto a mold wherein an inner diameter portion of the device isovermolded. A thermoplastic elastomer material is injected into the moldto form the inner portion of the housing 12. It is understood that anadhesion promoter may be used wherein the adhesion promoter is appliedto the inner surface of the spine member 22 prior to overmolding thethermoplastic elastomer material. The adhesion promoter assists enhancesthe bonding of the thermoplastic elastomer material to the spine member22. In one exemplary embodiment, 3M Primer 94 sold by the 3M company isused as the adhesion promoter. It is also understood that the molds aredesigned such that openings are provided in the inner portion of thehousing 12 that are in communication with the recessed compartments50,52 that will receive the batteries 142.

Additional components are then ready to be attached to the spine member.As can be appreciated from FIGS. 15 and 16, the PCB member 140 of thecontroller 14 is formed with the necessary circuitry, other electricalcomponents, antennas, as well as the required sensors including thethree-axis accelerometer. In addition, the display 18 and indicatorsystem 20 components are also connected to the PCB member 140. It isfurther understood that the input button 16 is formed in a two-shotinjection molding process wherein the rigid base member is integrallyconnected to the flexible cap (FIGS. 17-18). The input button is alsoconnected to the PCB member 140. The PCB member 140 is connected to thespine member 22. The PCB member 140 is wrapped onto the spine member andfollows the contours of the spine member 22 generally insurface-to-surface engagement including at the flexible zones 46,48 ofthe spine member 22. (FIGS. 6, 15, 16) The PCB member 140 is fixedlyattached to the spine member 22. As discussed, this configurationassists in providing a more neutral axis wherein stresses from flexingare minimized. The ends of the leads of the USB connector 94 are alsosoldered onto the PCB member 140. The batteries 142 are inserted intothe battery compartments (FIGS. 19-20). The raised contacts arepositioned through the openings 59 in the battery compartment 50,52wherein the contacts mate with receiving contacts on the printed circuitboard. The battery closure members are fixedly attached to the innerportion of the device via screw fasteners (FIG. 2) wherein the batterycontacts are biased against mating contacts associated with PCB member140.

This intermediate assembly is then inserted into an additional mold foran additional overmolding process. The mold includes a tool that engagesthe first ring surface 82 and the second ring surface 86 of the inputbutton 16 to prevent the thermoplastic elastomer material from migratinginto the internal portions of the input button 16 (FIGS. 17-18). Thethermoplastic elastomer material is injected into the mold to completeformation of the outer encasement member 24. In one exemplaryembodiment, the spine member 22 includes a tube structure having a portopening 380 wherein the material is injected through the tube structureto form the outer portion of the outer encasement member 24. As shown inFIG. 19a , the port opening 380 is provided in an inclined surface inthe battery compartment 52 and is in communication with the tubestructure through the spine member 22. Once placed in the appropriatemold member, the injected material is injected through the port opening380 and flows in the mold to form the outer portion of the outerencasement member 24. It is understood that the port opening 380 couldbe located in either battery compartment or in other locations on thespine member 22. The port opening 380 could further include multipleport openings. Thus, the various components supported on the spinemember 22 are encased in the outer encasement member 24. Thethermoplastic elastomer material flows to and engages with a sidesurface of the input button 16 wherein further migration of the materialis prevented by the tool (See FIG. 6). Once the overmolding process iscomplete, the receiver portion of the latch mechanism and any desiredspacer element can be attached (FIGS. 2, 3 and 19). In suchconfiguration, it is understood that the housing 12 is easily flexibleto allow for placing the device on a wrist of a user. The device 10flexes at the flexible zones 46,48 of the spine member 22 wherein it isunderstood that the rigid segments with the batteries 142 mountedthereon move together. The elastic properties of the outer encasementmember 24 readily allow for such pivoting while providing sufficientstructure to protect the components supported by the spine member 22.

The device 10 is then formed and ready for operation (FIG. 2). Operationand other user experiences are described below.

The device 10 of the present invention has numerous alternativestructures and configurations. For example, FIGS. 21-38 discloseadditional embodiments of various components of the housing 12,controller 14, display 18 and indicator system 20 that can be utilizedin the device 10 and combined with features of the device 10 describedabove.

FIGS. 21a-d illustrate schematic side views of alternative embodimentsof spine members and batteries that can be used with the device 10 ofthe present invention. Similar structures may be referred to withsimilar reference numerals. The spine member 22 a has the multipleflexible zones 46 a,48 a along with the rigid or substantially rigidsegments or zones 42 a,44 a. FIGS. 21a-d illustrate the flexible zonesin the form of thinner portions of the spine member 22 a. The thinnerportions may correspond to more flexible regions while thicker portionsof the spine member 22 a may correspond to more inflexible areas orrigid zones. It is understood that the spine member 22 a more easilyflexes or hingedly pivots about the flexible zones. The rigid zones 42a,44 a might not be flexible to allow for non-flexible components suchas circuit boards, lighting systems, battery packs and other electronicsassemblies to be secured. For example, the rigid zones 42 a,44 a mayeach include a battery pack 142. Additionally or alternatively, one ormore of rigid zones 42 a,44 a may include circuitry for processing,storing and/or sensing athletic information. The display component maybe disposed in an additional central rigid zone generally extendingbetween the rigid zones 42 a,44 a supporting the batteries. The rigidzones 42 a,44 a may have a limited amount of flexibility to at leastallow for a predefined amount of expansion of device assembly 10.

As further can be appreciated from FIGS. 21a-21b , the lengths ofbattery packs 142 can be adjusted to increase or decrease batterycapacity. Due to the changes in the lengths of the battery packs 142,the length or other dimension of display components, indicator systemcomponents, or other controller components can also be affected. Forexample, if the length of battery packs 142 is increased, the size ofthe display or display may be decreased to compensate. Similarly, inFIGS. 21c-21d , the thickness of the battery packs 142 may be modifiedto adjust battery capacity and device life. By increasing thickness ofthe device rather than length, the size of flexible zones may bemaximized since there is no expansion of the battery pack 142 along thelength of device assembly 10. However, increasing thickness may alsoincrease weight and/or device circumference. The batteries 142 and rigidsegment or zones 42 a,44 a may be cooperatively dimensioned to provide adevice 10 having a suitable capacity to record activity and displayinformation prior to requiring recharging.

FIGS. 22 and 23 disclose components of a controller according to analternative embodiment of the invention. Similar components may bereferred to with similar reference numerals. The PCB member 140 supportsother components of the controller 14. The indicator system 20 may alsobe provided with separate light member compartments 180 and a covermember 182 positioned over the light members of the indicator system. Anadditional cover member 184 may be positioned over the PCB member 140 asshown in FIGS. 23a-c . It is understood that the controller as shown inFIGS. 23a-c can then be wrapped onto a spine member 22 and fixedlyattached thereto.

FIGS. 24-27 disclose display components of an alternative embodiment ofthe device 10. FIG. 24 discloses an exploded view of components of adisplay according to an alternative embodiment of the invention. Similarcomponents may be referred to with similar reference numerals. Thedisplay 18 in this embodiment has a plurality of light members 152operably connected to the PCB member 140 of the controller 14 andmounted to the spine member 22. A seal member 190 has an openingtherethrough and shaped to be positioned around the peripheral edges ofthe plurality of light members 152. A first cap member 192 having aplurality of apertures therethrough is positioned over the plurality oflight members 152. The apertures are positioned to correspond torespective light members. A pair of additional transparent cover members194 is positioned over the cap member 192. A single transparent covermember could also be utilized. As can be appreciated from FIG. 24, theseal member 190, cap member 192 and cover members 194 are positionedover the plurality of light members 152 of the display 18. The capmember 192 is sandwiched between the seal member 190 and the covermembers 194. When the plurality of light members 152 are illuminated,light can pass through the apertures of the cap member 192 and isviewable through the cover members 194.

FIGS. 25a and 25b disclose the cap member 192 in greater detail. The capmember 192 is configured to be positioned over the plurality of lightmembers 152 of the display 18. The cap member 192 has a convex outersurface. FIG. 25b discloses an underside view of the cap member 192shown in FIG. 25a . The cap member 192 has the plurality of aperturesthat generally correspond to the position of the plurality of lightmembers 152 of the display 18. As further shown in FIG. 26, eachaperture is in communication with a column 196 extending into theunderside of the cap member 192. As shown in FIGS. 26 and 27, eachcolumn 196 has a general frusto-conical shape. A bottom portion of thecolumn is dimensioned to completely surround the light member 152 of thedisplay 18. As can be appreciated from FIGS. 26 and 27, the cap member192 is positioned over the plurality of light members 152 wherein eachlight member 152 is positioned within a respective column 196 of the capmember 192. The outer encasement member 24 of the device 10 ispositioned over the cap member 192 and is structured and dimensionedsuch that when the light member is illuminated, light is viewablethrough the outer encasement member 24. As shown in FIG. 27, when thelight member is illuminated, the frusto-conical column 196 assists inreflecting light such that the light if directed in a more focusedmanner through the aperture and outer encasement member 24. It isunderstood that the outer encasement member in this embodiment couldhave an opening wherein the clear cover members 194 extends past theopening and wherein the light members are viewable through the opening.

FIGS. 28 and 29 show additional alternative embodiments of a display. InFIG. 28, a thin, transparent cover member 198 is positioned over theplurality of light members 152 of the display. A cap member 200 having aplurality of interconnected caps is positioned over the plurality oflights. Each cap is dimensioned to fit over a respective light member.FIG. 29 also shows a display utilizing a transparent cover member 202over the plurality of light members 152. A cap member 204 having aplurality of apertures is positioned over the cover member 202.

FIG. 30 shows a partial cross-sectional view of the USB connector 94.The USB connector 94 is connected to a distal end of the spine member22. The USB connector has the plurality of USB leads 98 and wherein theUSB leads 98 include ribs thereon thus having raised configuration. Asfurther shown in FIG. 30, the USB leads are connected to connectors thatextend through the spine member 22 and are operably connected to thecontroller 14.

FIGS. 31-33 illustrate an alternative fastening mechanism that can beused in the device 10 of the present invention. The fastening mechanism300 has cooperating components that can be operably associated with thehousing 12 of the device 10. The fastening mechanism 300 generally has afirst projection member 302 and a second receiver member 304. Similar toprior embodiments, the fastening mechanism incorporates a USB devicethat is configured to attach to one end of a housing 12 of the deviceassembly 10 on one side and to connect to a receiving end on the housing12 on the other side. For example, as shown in FIGS. 31a and 31b , a USBconnector 306 incorporated into the first projection member 302 isinsertable into the second receiver member 304. The USB connector issimilar in structure as prior embodiments and has a plurality of leads.The receiver member 304 includes an opening 308 or slot having a shapeand size corresponding to the size and shape of the USB connector 306.The opening 308 of the receiver member 304 may include a spring-loadedlatch 310 that is configured to secure the USB connector 306 to thereceiver member 304 upon insertion. The opening 308 or slot may extendthrough the entire receiver member 304 in a lengthwise direction. Thelength of the receiver member 304 may be less than the entire length ofUSB connector 306. In one example, the length of the receiver member 304may correspond to approximately one-half or one-third of the length ofthe USB connector 306. The spring-loaded latch 310 may extend out of andpast a rear portion of the receiver member 304 to align with one or moreportions of the USB connector 306 when the USB connector 306 is fullyinserted into receiver member 304.

FIG. 32a illustrates an interior view of the receiver member 304. Thelatch 310 pivots around a spring 312 and biases the latch 310 to alatching position. The latch 310 also has a finger 314 and a button 316for activating the latch 310. The latch finger 314 pivots in an oppositedirection to the button 316. By pressing the button 316, the finger 314may be dislodged from the USB connector 306 (FIGS. 31a-31b ), allowingthe USB connector 306 to be removed/detached from receiver member 304.

FIG. 32b illustrates a bottom surface of the USB connector 306configured to engage with the latch 310 of the receiver member 302. Thebottom surface of the USB connector 306 has a recess 318 which definesan engagement surface 320, wherein the latch 310 is configured to engagethe surface when USB connector 306 is inserted. In the illustratedarrangement, the recess 318 is on a surface of the USB connector 306opposite the USB connector leads.

Because the receiver member 304 may be shorter than the overall lengthof the USB connector 306, the end of the housing of the wearable deviceassembly 10 may include an opening having a length equal to a length ofthe USB connector 61 that remains exposed after insertion into receivermember 304.

FIGS. 33a-33d illustrate a process by which the USB connector 306 isinserted into the receiver member 304 and a further opening in an end ofthe housing 12 of the wearable device assembly 10 to which the receivermember 304 is attached. In FIG. 33a , the latch 310 may initially bebiased such that finger 314 protrudes into the opening in the housing12. As the USB connector 306 is inserted into the opening 308 of thereceiver member 304 and into the additional opening (as illustrated inFIG. 33b ), the finger 314 may be forced downward by the USB connector306 contacting an inclined surface of the finger 314. Upon the USBconnector 306 being inserted into the receiver member 304 and theopening to a point where the recess 318 is aligned with the latch 310,the finger 314 may protrude into the recess 318 and engage theengagement surface 320 due to the spring bias as illustrated in FIG. 33d. This engagement provides a secure connection between the USB connector306 and the receiver member 304. Accordingly, a fastening mechanism isprovided between the ends of the housing of the device 10.

FIGS. 34a and 34b disclose a spacer assembly or expansion element usedto increase the size of the wearable device assembly 10, and also can beused with the fastening mechanism 300 shown in FIGS. 31-33. Theexpansion element may also include an opening 336 into which a portionof a USB connector 306 may be inserted and engaged. FIGS. 34a-34b , forexample, illustrates an expansion element 330 having a connector portion332 configured to mate with and connect to an opening 334 in the housing12. This connection can take various forms. For example, a shape of theconnector portion 332 may match the shape and size of opening 334. Tofacilitate the use of the expansion elements, the receiver member 304may be removably detachable from the main body of the wearable deviceassembly 10. The expansion element 330 may then be inserted betweenreceiver member 304 and the end of the housing 12. Clasps or other typesof fastening mechanisms might also be included in the opening 334 and/orconnector portion 332 to provide a secure attachment. One end of theexpansion element 330 may include an opening 336 that is of similarshape and size to the opening 334 in the end of the housing 12. Thisallows the USB connector 306 to mate with the opening 336 in theexpansion element 330, in the event a user wishes to use one or moreexpansion elements. FIG. 34b illustrates the overall device assemblyupon insertion of the extension element 330 and connection of the USBconnector with the receiving portion.

FIGS. 35-37 illustrate another example alternative fastening mechanismin which a micro USB connector may be used instead of a full sized USBconnector. In this arrangement, the micro USB connector may be taperedin shape to help simplify the engagement between the micro USB connectorand the receiving portion of the other end of the wearable deviceassembly 10. The fastening mechanism 350 has cooperating components thatcan be operably associated with the housing 12 of the device. Thefastening mechanism 300 generally has a first projection member 352 anda second receiver member 354.

As illustrated in FIGS. 35a-c , the first projection member 352 supportsa micro USB connector 356. The micro USB connector 356 may include metalpins 358 that may be used to secure the micro USB connector end 356 tothe receiver member 354 of the wearable device assembly 10.

FIGS. 36a and 36b illustrate different perspective views of the receivermember 354. As illustrated, the receiver member 354 has an openinghaving hook members 360 supported therein for latching onto the metalpins 358 (of FIGS. 35b and 35c ). In an exemplary embodiment, the hookmembers 360 may be biased with a spring member 362 and moveable againstthe spring bias by a depressible button 364.

FIGS. 37a-e illustrates an example process by which the micro USBconnector 356 of the first projection member 352 is connected to thereceiver member 354. As the micro USB connector 356 is inserted into theopening of the receiver member 354, inclined surfaces of the hookmembers 360 engage the metal pins 358 and are forced upwards against theforce of the spring 362. Once inserted further into the opening, thehook members 360 pass beyond the metal pins 358 wherein the spring 362biases the hook downwards wherein the hook members 360 engage againstthe pins 358 wherein the latch mechanism is in a latched position. Theuser may depress the button 364 to disengage the members 352,354.

FIGS. 38a and 38b illustrate views of the fastening mechanism 350 ofFIGS. 35-37 using an expansion element 370. In particular, the receivermember 354 may be removably detachable from the housing 12 of thewearable device assembly 10 so that expansion elements such as theexpansion element 370 may be inserted between the receiver member 354and the housing 12 of the wearable device assembly 10. Each expansionelement 370 may include an opening 372 into which receiver member 354may be inserted and secured. FIG. 38b illustrates a wearable deviceassembly 10 having the micro USB connector 356 and the expansion element370 or spacer inserted.

It is understood that other alternative fastening mechanisms could beutilized to releasably connect distal ends of the housing 12 of thewearable device assembly. Other structures could include interferencefit connections, hook and loop fasteners, or other buckle typeconfigurations. The housing 12 could also have a permanent annularconfiguration while having an expanded configuration to allow a user tofit the assembly onto the wrist etc.

As discussed and shown herein, the various components of the wearabledevice assembly 10 are connected and supported by the spine member 22wherein the elastomer material is formed over the components to placethe device 10 in its final form as shown in FIGS. 1 and 2. As can beappreciated from the Figures, the fastening mechanism 26 can beunlatched wherein the device 10 can be positioned around a wrist of theuser and the fastening mechanism 26 can be subsequently placed in alatched position. The user can wear the device 10 at all times ifdesired.

When worn by the user, the device 10 can track activity of the user. Itis understood that the controller 14 of the device 10 has certainalgorithms associated with the controller and sensor to process andutilize data sensed by the sensor(s). It is understood that thecontroller can utilize a single algorithm or multiple algorithms asdesired. Certain algorithms may be utilized for specific activityengaged in by the user. The controller 10 can also be configured suchthat certain algorithms are automatically selected based on the datasensed by the sensor. In an exemplary embodiment, an input can beprovided to the device 10 for activation wherein the device 10 beginstracking activity of the user. For example, the sensor such as thethree-axis accelerometer can sense movement of the user wherein thedevice 10 records data associated with such movement. Activity trackedcan vary including steps taken by the user, energy expended by the useror other metrics or parameters. Certain parameters tracked can alsoinclude speed and distance, heart rate, or other parameters. Additionalprocessing may be employed with the sensor, algorithm and sensed data.In one exemplary embodiment, the device 10 may utilize a transferfunction/algorithm that translates the data measured by theaccelerometer and energy expenditure, wherein acceleration is mapped toapproximate oxygen kinetics (calories burned). The display and/orindicator system may display indicia indicative of such activity. Thedevice may also wirelessly interact with a mobile device associated withthe user or a remote website such as a site dedicated to fitness orhealth related subject matter. At some predetermined time, the user maywish to transfer data from the device to another location. As shown inFIG. 44 the user may unlatch the device 10 and plug the USB connector 94into a computer. In response, data stored on the device 10 may betransferred to the user's computer and/or to a remote site for furtherprocessing and display. Data may also be loaded onto the device 10 fromthe user's computer or remote site. The device 10 and/or computer may beconfigured such that the user is prompted to commence a data transfer orthe data transfer can commence automatically once the device 10 isplugged into the port of the computer. Such data may be configured totrigger operational events on the device 10 such as illuminating thedisplay or indicator system based on time, activity currency or othervariables. When the device 10 is plugged into a computer to sync andtransfer data, certain light members of the indicator system may beilluminated to indicate a syncing process. The batteries of the device10 are also charged when the USB connector 94 is plugged into the user'scomputer. It is understood that the device 10 can also be configuredsuch that data transfer and/or device charging can be done via wirelessand/or wired connections. For example, the device 10 may be configuredfor re-charging batteries via induction charging. The device 10 couldalso be configured to automatically transfer data wirelessly if thedevice 10 senses another suitable paired device. Once a syncing processis complete and the device 10 is sufficiently charged, the device 10 canbe removed from the computer, and again worn by the user and activatedto begin detecting activity. Further user interfaces and userexperiences associated with operation of the device will be describedbelow. In some arrangements, the indicator system (e.g., indicatorsystem 20) may be a second display. The indicator system 20 and thedisplay 18 may be controllable independently of one another.

FIG. 43 is an example block diagram of a wearable activity detection andtracking device 4300. The device may include a variety of componentsincluding a main controller or host processor 4301 configured to executeinstructions and control other components of the device 4300 inaccordance with the instructions. The device 4300 may further includememory for storage of data and instructions including volatile andnon-volatile memory such as random access memory (RAM) 4303, read-onlymemory (ROM) 4305 and storage 4307. Additionally, the device 4300 mayinclude a charging component 4309 for charging one or more batteries(not shown) powering the device 4300. The device 4300 may furtherinclude various input and output adapters and other components includingan ambient light sensor 4311, a display adapter 4313, an accelerometer4315 and input adapter 4317. Ambient light sensor 4311 may be used todetermine a level of brightness for one or more displays forviewability. Light sensor 4311 may also be used to determine a generaltime of day. Input adapter 4317 may be configured to receive and processvarious types of input including button presses, touch input, scrollwheel input and the like, depending on the types of input devicesincluded in the device 4300. Accelerometer 4315 may be configured fordetecting movement of the wearable device and the user when the deviceis worn. In some examples, accelerometer 4315 may be a six-axisaccelerometer. Other sensors including heart-rate sensors, temperaturesensors, humidity sensors and the like may also be included in thedevice 4300.

Communication by the device 4300 may be performed through wired andwireless connection means. In one example, device 4300 may include aradio component 4319 configured to communicate with other deviceswirelessly through radio frequency transmissions. The radio component4319 may correspond to a BLUETOOTH transceiver, an RFID device, a Wi-LANtransceiver, cellular transceiver and the like and/or combinationsthereof, and/or may include a dedicated processor. Display adapter 4313may be configured to control one or more displays of the device inconveying various activity information, interaction information, alerts,notifications and the like. In one example, display adapter 4313 may beconfigured to control a first display independently from controlling asecond display of the device 4300. The wearable device may furtherinclude location determination components such as global positioningsystem (GPS) component 4321. Location determination may also beperformed using other devices including a cellular transceiver (e.g.,based on cellular triangulation). Components described herein may becombined into a single device or may be distributed over multiplecomponents. Moreover, additional or alternative components may be usedto provide additional or alternative functionalities.

For example, the device 10 may provide a daily progress goal indication.The user may set a goal to the device 10 wherein the user is to completea certain amount of activity during a day, or 24 hour period or lessertime period. The device 10 detects and records the activity of the useras the user progresses through the day. Based on the activity sensed,the controller illuminates light elements on the indicator systemcorresponding to the progress towards the goal set on the device 10. Forexample, a number of light elements on the indicator system based on theamount of progress (e.g., a %) toward the user's goals. Additionally,the color of the illuminated light members indicates how active the userwas over the past predetermined amount of time. For example, theindicator system could be illuminated to show how active a user has beenfor the past hour on a color scale from red to yellow to green with ared color being least active and a green color being most active. Whenthe user engaged in enough activity wherein the goal is reached, all ofthe light elements of the indicator system will be illuminated. One ormore of the light elements (e.g., on a side indicator system or display)may also blink on and off to indicate the goal has been reached. Forexample, the leftmost light element may blink on and off every 5 secondsuntil receiving some user interaction (e.g., user input through aparticular input device or any input device) or upon the goal beingreset (e.g., at midnight for a daily goal or other specified automaticor manual reset time).

Alternatively or additionally, a current progress indication may also beprovided by blinking or otherwise illuminating a lighting element of anindicator system (e.g., indicator 20) corresponding to a current amountof progress toward reaching the goal. For example, the current progressindication may be provided whenever a user's progress reaches anotherlevel (e.g., another lighting element) on the indicator system. In aparticular example, if each segment of indicator system 20 correspondsto a different interval of progress, once the user changes from acurrent interval of progress (e.g., 10-25% progress towards goal) toanother interval of progress (e.g., 26-40% progress), progressindication may be provided. Accordingly, upon reaching the other levelof progress, the corresponding area or element of the indicator systemmay be illuminated, blinked or the like for a specified amount of time(e.g., 5 second cycles for 30 seconds). Current progress indication mayalso be provided whenever any change or specified threshold amounts ofchange occur. According to some aspects, the current progress indicatormay be provided when the device is in one or more types of sleep orinactive states. The progress indicator may be provided periodically orbased on some other defined schedule. Other types of progress indicatorsmay also be used including audible and haptic indicators.

Such a blinking configuration can be triggered even when the device isnot being interacted with by the user. An audible alarm could also beprovided via a speaker operably associated with the controller andsupported by the housing. The device 10 could also have an initialdefault goal that can be subsequently changed by the user. If a new goalis set, a certain light element of the indicator system can initiallyblink to indicate to the user where on the indicator system the goalprogression will start. Goals and goal tracking are described in furtherdetail herein. Additionally or alternatively, goal and activityinformation may be reset at a predetermined time each day or at theexpiration of the goal time period.

As discussed, the device 10 tracks activity of the user and displaysindicia indicative of such activity such as on the indicator system 20.The device 10 is capable of displaying data according to severaldifferent features. In one exemplary embodiment, the indicator system 20has a plurality of twenty light members. Each light member of theindicator system may display a plurality of perceptively differentcolors including colors such as red, yellow, green, orange, white, blueor other colors as desired. A certain number of light elements can beilluminated to indicate a level of activity (e.g. one illuminated lightelement for low activity and twenty illuminated light elements for highactivity), and a certain color could be used to indicate a level ofactivity (e.g., red color for low activity, yellow color for mediumactivity and green color for high activity). Combination of suchilluminated light elements can also be employed. In addition, certainilluminated colors or illuminated color schemes could be used forspecific designations such as to designate a specific sponsored event,to designate that the user is performing activity in support of acharity, or to designate that the user is interacting with another user.The plurality of light elements of the indicator system can also bedesignated into separate segments to display indicia according toaspects of the invention as described herein.

According to one or more configurations, a wearable athletic performancedevice such as wearable device 4300 (FIG. 43) may include multiple modesand functions. In one example, upon the device being activated for thefirst time, the device may enter an initial start-up mode that displaysan icon indicating that the device is to be plugged into a computer or apower source. In this mode, low battery warnings might not be providedand the icon indicating that the device is to be plugged into a powersource may be sufficient. Once connected to a computer, the device mayenter a setup mode, allowing the user to configure various aspects ofthe device through a program executing on the computer to which thedevice is connected. In a particular example, the setup program on thecomputer may automatically be installed on and launched by the computerupon connection of the device. The setup program, in some instances, maybe stored on the device and transferred to and installed on the computerupon connecting the device. Additionally or alternatively, in the setupmode, a battery icon may be displayed on a display (e.g., top display orside display) of the device indicating a currently battery level. Thebattery indication may remain on the display of the device until thedevice assembly is unplugged from the computer. In some arrangements, inorder to progress from the setup mode (e.g., to a subsequent mode suchas an activity tracking mode), the user may be required to complete asetup process through the setup program. If the user unplugs the deviceprior to completing the setup process, the device may revert to apre-setup mode (e.g., the initial start-up mode). If the user completesthe setup process through the setup program, the device may enter asubsequent mode such as an activity evaluation mode. In some examples,the activity evaluation mode might only be available or activated oncethe device has reached a certain amount of battery charge (e.g., 20%,30%, 40%, 50%, 65%, 75%, 100%, etc.). In other examples, the activityevaluation mode may be available or activated regardless of a level ofbattery charge.

During initial setup (e.g., for a first user), the user might not beable to use the device until the device has a threshold amount of chargesuch as 90%. For example, the device might not provide any interactivityincluding functional or information displays, synchronization functions,goal setting options and the like. Additionally or alternatively,activation of the device to begin recording athletic activity mayrequire the user to complete a setup process on the device through thedevice itself or another computing device (e.g., mobile communicationdevice, desktop computer, laptop computing device, etc.). In oneexample, if the user does not complete the setup process (e.g., byentering all required information and selecting a “COMPLETE” or “START”button in setup software), and attempts to use the device (e.g., bydisconnecting the device from another computing device through whichsetup is performed), the device may be reset to a pre-setup state suchas an initial start-up mode. In one example, all information previouslyentered in the setup mode may be deleted. In other examples, theinformation previously entered may be stored and pre-populated when theuser repeats the setup process.

The device may wait for a signal indicating completion of the setupprocess before unlocking activity tracking functionality. As noted, thissignal may, in some arrangements, be provided from another computingdevice if the setup is performed through that other computing device.The signal may correspond to an indication that setup is complete, orthe signal may correspond to a determination that all requiredinformation such as user profile data, goal information and the like hasbeen entered and synchronized with the device. Moreover, the device mayprovide a signal such as a haptic, visual and/or audible signal to theuser that the device may be used to track athletic activity. Forexample, a message such as “GO!” may be displayed on the device.Alternatively, if setup is not complete (e.g., not all required data hasbeen inputted), the device may display a message such as “NO GO” or“ERROR.”

The activity evaluation mode may include a specified period of timeafter initial activation of the device, during which the user's activitylevel is measured and recorded. The activity evaluation mode may be arequired activity prior to full activation of the device (e.g.,unlocking all functionalities). Alternatively, the evaluation mode mightnot be required or included in the device. FIG. 45 illustrates anexample flow diagram for an activity evaluation mode of the device. Flowdiagram 4500 may represent a function or status flow upon the activityevaluation mode being activated. In a particular example, the period oftime during which the user's activity level is measured and recorded maybe 1 day (e.g., 24 hours). However, any period of time may be usedincluding 30 minutes, 1 hour, 6 hours, 12 hours, 1 week, 5 days and thelike. In some arrangements, the period of time may be used to calibratethe device and/or to establish a baseline activity level for a wearer ofthe device. Calibration may include determining a conversion factorbetween a detected athletic performance metric value and an actualperformance metric value. For example, if the device detects that theuser ran 0.8 miles, but the actual distance run was 1 mile (e.g., basedon a user's own measurement or determination), the calibration may set aconversion factor of 1.25 to account for the discrepancy. Baselinemeasurements, on the other hand, may be used to determine a user'scurrent and/or typical (e.g., average) athletic activity level and maybe used to define goals and determine trends in a user's athleticactivity.

The process of diagram 4500 might only be executed if the devicedetermines that the initial calibration or baseline activity measurementhas not been performed or has not been completed. For example, thedevice may set a flag upon performing the initial calibration orbaseline activity level measurement so that the evaluation mode is notre-activated again. Accordingly, if the flag is not set, the device mayundergo the process of diagram 4500. Alternatively, the device may checkfor calibration or baseline activity measurement data to determine ifthe initial calibration or baseline measurement was performed. In someexamples, a flag might be set if the initial calibration and/or baselineactivity level measurement has been completed (e.g., once the initialtime period has passed or expired).

The process of diagram 4500 may include a time remaining check todetermine whether the evaluation time period has expired, a messagescheck to determine whether messages have received on the device or on aconnected communication device, a battery check to determine a level ofcharge available and a battery low warning display if the level ofcharge is below a specified threshold. Additionally or alternatively, amemory check may be performed to determine whether an amount ofavailable memory in the device is low. If so, a warning may be displayedand/or the device might not allow further data tracking and storing. Forexample, data detected using the accelerometer might not be recorded orstored in the device. Alternatively or additionally, the device maydisplay a “SYNCH” message to encourage the user to synchronize data withone or more other devices so that memory may be freed.

The various checks and warning messages may be performed and displayed,respectively, upon a button on the device being pressed or otherinteraction with an input component on the device when the device is ina sleep mode. A sleep mode may correspond to a mode in which the displayis not activated. For example, the sleep mode may correspond to a modein which one or more displays are deactivated after a specified amountof time of no user interaction (e.g., no pressing of one or more buttonsor other interactions with input mechanisms on the device). In aparticular example, a user may press a button to view an amount ofcalories burned. The display on the device may indicate the amount ofcalories burned and subsequently turn off if no further user interactionis received. A display may include static displays of information (e.g.,text, icons, images, symbols, etc.) as well as animations. In somearrangements, information may also be conveyed audibly or haptically.According to some configurations, a sleep mode may correspond to adeactivated display mode while an inactive or low power mode maycorrespond to deactivation of one or more additional components after acertain amount of non-active time. A sleep mode need not be based on anamount of inactivity time.

The timeout period for entering a sleep or inactive mode may differ fordifferent functionalities or information displays. For example, a linkor pair function may have a longer timeout period since it may take alonger amount of time to establish a link than to enter a tag, forinstance. Moreover, the timeout period may differ between differentdevice modes such as between the information display mode or loop andthe action mode or loop.

The sleep mode may include a state in which both of the display andindicator system are not illuminated. By depressing the input button, auser can check on activity progress. In response to depressing the inputbutton, the indicator system can illuminate in an animated fashion withindividual light members being progressively illuminated until the lightmembers reach a number corresponding to the user's activity level. If auser does not press the button on the device or otherwise interact withthe device (e.g., movement of the device, using any input elements ofthe device, etc.), the device may enter the sleep mode or an inactivestate after a predetermined amount of time (e.g., 4 seconds, 30 seconds,1 minute, 2 minutes, etc.), which may be user-configurable. The devicemay further provide a time countdown display as part of the process ofdiagram 4500. The time countdown may indicate an amount of timeremaining for the evaluation period. For example, the evaluation timeperiod may start at 24 hours and count down from there. If theevaluation period is over (e.g., the amount of time remaining is 0), thedevice may display an evaluation completion messages instead of thecountdown message. In some examples, the time countdown or evaluationcompletion message might always be the first information interface to bedisplayed on a first button press or other user interaction of the dayor of an activity time period (e.g., a goal time period). In otherexamples, the time countdown or evaluation completion message mightalways be displayed first based on other rules including upon detectingthe first button press or user interaction of the hour, minute, 12hours, morning, afternoon, evening and the like. Yet other triggers mayinclude particular buttons or other specified input mechanisms beingpressed and/or types of input including an amount of time a button ispressed, a pattern of button pressing (e.g., 4 short button presseswithin 5 seconds or 1 short button press followed by a 2 second buttonpress or the like). Such display rules may be used to maximize relevanceof displayed information to the user. If the device determines that theevaluation period has been completed, instead of displaying a countdown,the device may display a completion celebration message followed by aplug icon or animation requesting that the user connect the device tothe computing device to synchronize the data (e.g., uploading therecorded activity information to the computing device).

Upon receiving further button presses (or user interactions of differenttypes or of the same type), the device display may be scrolled betweenan accumulated points display (e.g., a measure of athletic activitydisplay), a time of day display, a calories display, a steps display anda messages display. In some examples, the messages display might only beshown if there are messages on the device or on the connectedcommunication device. For example, the device may be wirelessly or wireconnected to a communication device such as a mobile phone. Accordingly,the device may be configured to detect (e.g., receive notifications of)messages on the mobile phone. The messages may include voice mailmessages, electronic mail messages, text messages, multimedia messagesand the like. If no messages are available, the device might not displaythe messages display (e.g., rather than display 0 messages, the messagesdisplay might not be provided). In some arrangements, the device mightonly provide an indication of a number of new messages or unread/unheardmessages. Upon an evaluation mode time period expiring, one or more ofthe metrics or information displays may be hidden and might no longer beaccessible and viewable. For example, the activity points display, thecalories display and the steps display may be hidden or not shown,leaving time of day and/or the number of messages as the only viewableor accessible displays once the evaluation mode time period has expired.

According to some configurations, completion of the evaluation mode onthe device may be required to enter an activity goal tracking mode. Inone example, completion of the evaluation mode may include connectingthe device to a computing device and synchronizing the data with thecomputing device. The device may synchronize wirelessly (or using awired connection) with a mobile device in some arrangements. Thecomputing device and/or software executing thereon may subsequentlytransmit a signal to the device activating the activity goal settingmode. In some examples, the synchronization may be uploaded to a remotenetwork site. Accordingly, activation of the activity goal tracking modemay be authorized or otherwise specified by the remote network site upondetermining that the evaluation period has been completed and activitydata for that period of time has been synchronized. Alternatively oradditionally, the wearable device may independently, or jointly withanother device or system, determine whether the evaluation time periodhas been completed and activate the goal tracking mode upon determiningthat the evaluation time period has been completed.

The activity goal tracking mode may include two user interfacesub-modes: an information loop mode and an action loop mode. Theinformation loop may include a first set of interfaces displayingactivity and time information to the user while the action loop mayinclude a second set of interfaces providing accessibility to variousfunctions using the device. The information display loop may beactivated by a button press of a first duration while the action loopmay be activated by a button press of a second duration. In one example,the first duration may be 0.5 seconds or less and the second durationmay be more than 2 seconds. Other durations and interaction rules may bedefined for activation of the various loops within the activity goaltracking mode. Additionally or alternatively, information or interfacesprovided in each of these modes may be presented in different manners tohelp the user differentiate between the two modes or loops. For example,interfaces of the information display loop may scroll onto the displayin a first direction (e.g., horizontally) while interfaces of the actionloop may scroll onto the display in a second direction (e.g.,vertically). The direction in which the various information displayloops and/or specific display items are scrolled onto the display orotherwise appear on the display may be configurable. For example, a usermay define a scroll direction on a separate computing device (e.g.,mobile communication device, desktop computer, laptop computer, etc.)having software for configuring the athletic activity monitoring device.In another example, the athletic activity monitoring device may haveconfiguration options and receive user configuration input itself. Thus,the information display loop may be configured to not scroll (e.g., theinformation will be displayed/appear without scrolling) or may beconfigured to scroll in a similar direction as the action loop.

Additionally or alternatively, scroll directions and displayorientations may automatically change based on an orientation of thedevice. For instance, if the user wears the device on his right wrist,the device may orient characters, numbers and other display informationin a first arrangement to facilitate viewing and readability from theright wrist. On the other hand, if the user wears the device on his orher left wrist, the device may automatically change the orientation ofthe display and/or animation or movement directions to facilitateviewing and readability from the left wrist. The change in orientationof the device may be detected based on one or more sensors or throughuser input. In one example, the change in orientation of the device maybe detected via an accelerometer included therein. In other examples,the direction of scrolling might always be defined as from a button side(e.g., input device side) to a side away from the button or inputdevice. Thus, changing an orientation of the device (e.g., handedness)might not affect the direction of scrolling or animation in somearrangements.

In some arrangements, a worn monitoring device may include a touchsensitive display with selectable options displayed in various sectionsof the display. Upon selecting an option the user may be presented witha further level of options and so on. Selection of an option may beperformed using touch input, physical gestures (e.g., waving the user'swrist in a particular pattern), touch gestures and the like. Physicalgestures and movements may be detected using an accelerometer, agyroscope and/or other sensors. The touch sensitive display may be usedinstead of or in addition to a button input device or other types ofinput devices. Accordingly, in some examples, a user may have multipleinput devices through which additional types of inputs and combinationsof inputs may be entered.

FIG. 46 illustrates a process flow for an information display loop inthe goal tracking mode. The goal tracking mode may include tracking useractivity when a goal is set and when a goal is not set. In theinformation display loop, the device may initially perform a series ofchecks 4601 upon detecting user interaction or input such as a buttonpress. In some arrangements, the series of checks 4601 might only beperformed on a specified schedule (e.g., once an hour, once every 30minutes, once every 5 minutes, once every 30 seconds and the like).Accordingly, the series of checks is set to be performed only once everyminute, the device might only perform the checks 4601 once if the userpresses a button more than one time during that 1 minute period.

Warning messages may be automatically scrolled from one to another untila first activity metric (e.g., time, calories, activity points,distance, etc.) is reached without requiring any additional user input.In other examples, a user may be required to provide user input toprogress from one warning message to another or from warning messages(which may be scrolling through automatically) to a first activitymetric display.

Upon completing checks 4601 and displaying any applicable warningmessages, the device may proceed to display a metric or display mostrecently viewed prior to the device exiting the information display loopby, for instance, entering a sleep mode or inactivity mode. For example,if a user does not interact with the device for a specified amount oftime (e.g., 1 second, 3 seconds, 5 seconds, 10 seconds, etc.), thedevice may time-out from the information display loop by deactivatingone or more displays (e.g., to conserve power) and/or other devicecomponents. In some arrangements, the number of activity points mightalways be displayed first upon first button press (or other userinteraction) when the device is used or when the device is being usedfor the first time or when the device has been reset (e.g., instead ofdisplaying the most recently viewed metric). In another example, a timeof day might always be displayed as the first information display upon afirst button press, reset and the like. Metrics or displays may includeactivity points, time of day, calories, steps, messages and the like andmay be toggled on and off from the information display loop. Forexample, a user may elect to remove calories and steps from theinformation loop such that calories and steps are not displayed as auser scrolls through the activity metrics and information.

FIGS. 47A, 47B and 48-52 illustrate example device interface displaysthat may be provided during the information loop. According to one ormore aspects, the activity information included in the information loopmay include different activity metrics or types of information thaninformation that is viewable or accessible in the evaluation mode. Inone example, the information loop may include at least one metric thatis not included in the information interfaces of the evaluation mode.

FIGS. 47A and 47B illustrate activity point displays. In FIG. 47A, forinstance, the device may initially display an activity point symbol intop display 4701 along with a display of a current amount of accumulatedactivity points 4703 and an indicator of a target level of activitypoints 4705 in side display 4707. The amount of accumulated activitypoints 4703 may be represented by a number of lights (e.g., LEDs) orilluminable segments that are activated alongside display 4707. If thereare 20 lights or illuminable sections, for instance, each light orsection may represent 5% of the goal. Accordingly, if a user hascompleted 50% of the goal, 10 indicator lights or sections may beilluminated. In another example, 99% or 99.99% of the goal amount may bedivided evenly or otherwise amongst all but 1 of the illuminablesections. The last section might only be illuminated when the goal isachieved by completing the last 1% or 0.01% of the goal. Accordingly, ifthere are 20 lights, each of the first 19 lights may represent 99.99%/19of the goal. The last section or light may represent the last 0.01% ofthe goal.

In some arrangements, the lights alongside display 4707 may differ incolor or be configured to change colors depending on a level of activityachieved. For example, the colors of the lights in display 4707 maytransition from red to green going from right to left (or,alternatively, left to right). The lights in display 4707 may changecolors such that all activated lights display the same color dependingon the level of user activity. For example, if a user has accumulated alow level of activity points, 3 out of 20 lights may be illuminated andthe lights may be illuminated in red while if the user has accumulated amoderate level of activity points, 10 out of the 20 lights may beilluminated, all in yellow. In yet another example, the lights may flashor otherwise be animated to reflect an activity level. In a particularexample, the lights may flash faster as the user accumulates moreactivity points. Various other combinations of colors, patterns,animations and the like may be used to convey the activity level.

The display of the indicator and the activity points level may beanimated in one or more configurations. For example, the indicator mayscroll onto the display 4701. Additionally, the lights or illuminablesections of side display 4707 may be illuminated in sequence (e.g.,right to left) at the same rate as the indicator scrolling to a finalposition on display 4701. The target light or section of side display4707 may blink a certain number of times to represent the targetactivity level. Once the points icon or indicator has been displayed fora specified amount of time (e.g., 1 second), the number of activitypoints may be displayed in top display 4701, replacing the icon orindicator. Displaying the icon or indicator may notify the user of themetric that is about to be displayed. The metric values may be displayedfor a specified amount of time such as 2 seconds, 3 seconds, 5 seconds,10 seconds, etc. The amount of display times described herein may beuser-configurable in some arrangements. In some instances, display ofthe number of activity points may cause the side display 4707 to becleared (e.g., all lights or illuminable sections deactivated). In otherarrangements, the device may maintain side display 4707 with theactivity level and target information even after the number of activitypoints is displayed in top display 4701.

FIG. 47B illustrates an example display in which the number of sidedisplay elements 4711 corresponding to a current goal progress areilluminated in a sequenced fashion. In one example, the rate at whichthe number of side display elements 4711 are illuminated corresponds toa rate at which the amount of activity points accumulated is scrolled onor otherwise displayed on top display 4715.

FIGS. 48-50 illustrate additional examples of activity metrics includingtime (FIG. 48), calories (FIG. 49) and steps (FIG. 50). The display ofthese additional activity metrics may operate similarly to the displayof activity points. Although not illustrated, the side display may alsobe used to track a goal specific to each of the activity metrics.Accordingly, a user may set different goals for each of the variousactivity metrics and track the goals separately. The device may, uponreceiving user interaction or actuation (e.g., a button press) todisplay a particular metric, determine whether a goal is set for thatmetric. If so, the device may activate and display goal information inthe side display as well. The device may cycle through the variousmetrics and information types automatically or upon a user's buttonpress. However, in some configurations, multiple button presses (orother type of user input) within a specified amount of time (e.g., 0.5seconds, 1 second, 2 seconds, etc.) of each other or during the samedisplay (e.g., a calorie display) might only be registered as a singleuser input such as a single button press. Other types of inputs may alsobe used to register the same functionality or results. For example, ifanother type of input device such as a touch-sensitive display isincluded in the device, touch-sensitive input may be used to interactwith and actuate functions and the like. In yet other examples, inputmay correspond to physical motions and gestures.

FIGS. 51 and 52 illustrate example interfaces that may be displayed upona user reaching a target or goal. The goal celebration may be displayedafter displaying an activity points total or after displaying any othermetric for which the goal is set. Alternatively, the goal celebrationmay be displayed without displaying the metric value. The goalcelebration message may include a user specified or selected graphic ormessage. Alternatively or additionally, a side display of the device mayprovide an indicator that the goal has been reached regardless ofwhether the device is currently displaying the information loop. Forexample, upon reaching the activity point goal, the side display mayilluminate one or more of the lights or illuminable sections in a staticmanner or in an animated fashion (e.g., blinking or activating thelights in sequence from left to right or the like) to indicate the goalhas been reached. In a particular example, a left most illuminablesection or light may blink to indicate that the user has reached his orher goal. The device may stop indicating goal completion upon entry intoa sleep mode, but reactivate the goal indication upon exiting the sleepmode (e.g., upon an activity sensor detecting movement or activity). Thegoal completion indicator may also stop flashing or blinking after agoal celebration display is initiated (e.g., pressing a button todisplay a goal celebration image or icon). Goal celebration messages andgoal achievement indicators may be toggled on or off depending on userpreferences. In one or more arrangements, the device may also display anamount of activity points still needed to accomplish the goal. Inaddition to goals, medals or and other achievements may be indicated aswell.

FIG. 53 illustrates another example series of device displays indicatingthat a user has completed his or her goal. In particular, the wearabledevice assembly displays a symbol such as a medal 5301 representing goalcompletion. Goal information may further be displayed automatically(e.g., after displaying medal 5301) or upon a user selecting button5303. The additional goal information may include a message thatindicates a goal was met and, in some cases, if the user exceeded thegoal by a certain amount (e.g., 50 calories or 50 minutes or 50 miles).Indicator lights 5305 may also indicate goal completion by illuminatinga predefined light such as the right most indicator light 5307 and, insome arrangements, illuminating the light in particular color such asgreen. The lights may be illuminated from left to right or right to leftas the user progresses toward a goal. The side display may also indicatewhen a goal has been exceeded by a specified amount differently thanwhen a goal has been met (e.g., reaching the goal but not achieving thespecified excess amount). For example, the side display may illuminateevery other lighting element to indicate that the user exceeded the goalby 10% or an absolute amount of a metric. If the user exceeds the goalby 25%, the side display may alternate illuminate of a left half of theside display and a right half of the side display. Any various patterns,animations, lighting configurations, colors and the like may be used.

FIG. 54 illustrates an example scrolling message that may be displayedon the wearable device assembly upon user completion of an athleticgoal.

FIG. 55 illustrates an example user interface that may be displayed on awearable device assembly upon setting a new goal. New goals (e.g., uponcompletion of a previous goal) may be defined by a user or may beadaptively controlled and defined. In one example, the wearable deviceassembly may automatically define a user's goal by increasing the amountof distance run, calories burned, weight lifted, heart rate reached,time performing athletic activity and/or combinations thereof by apredefined amount or percentage (e.g., 100 calories, 10%, 0.5 miles,etc.) once a previous goal and/or goal time period has been completed.If a user did not complete the previous goal, however, the device mightnot increase the goal and/or may increase the goal by a lower amountthan if the user had completed the goal. In some arrangements, theadaptively defined goal may be defined based on an overall goalspecified by the user. For example, if the user has indicated a desireto train for a marathon, the wearable device assembly may define a newgoal based on a workout plan to help the user reach a level of endurancethat will allow him or her to run 26.2 miles.

FIG. 46A illustrates another example information loop that may be usedinstead of or in addition to the example loop of FIG. 46. For example,FIG. 46A illustrates a different order in which metrics such as activitypoints, calories, steps and time of day and messages or information suchas goal celebrations may be displayed. Additionally, information displayfunctionality may also differ. For example, in the loop of FIG. 46A, ifthe user presses a button or otherwise provides input while the deviceis in a sleep mode or deactivated state, the device may return to ametric most recently viewed prior to the device entering the sleepmode/deactivated state or leaving the information loop. For somemetrics, both a metric name and the metric value may be displayed. Forothers, only the metric value may be displayed. For example, if thedevice times out at a time display in the information loop, uponreactivation of the information loop, the device may display the timewithout the “TIME” label. However, for other metrics such as activitypoints, calories and the like, the label may be displayed, even when theinformation loop timed out during display of those metrics.

There may be exceptions to this display configuration including thefirst time the device is used after setup or a hard reset and when adaily goal is reached. When the device is first used after setup or hardreset, the activity points display may always be displayed first. When adaily goal is reached, the goal celebration message may be displayedfirst regardless of the metric that was most recently viewed. Once thegoal celebration message has been displayed for a specified amount oftime, the display loop may progress to the activity point metric, again,regardless of the metric that was most recently viewed. This may providethe user with a logical progression in information displays and alertthe user about a completed goal. After the goal completion message isdisplayed a first time, the goal completion message might not be firstdisplayed in a subsequent activation of the information loop. Instead, ametric most recently viewed in the information loop may be displayed asdiscussed herein. Additionally, the goal completion message may become aseparate display item, independent from the activity point display,after being displayed for a first time, such that the activity pointdisplay is no longer displayed automatically after the goal completionmessage. Multiple types or predefined goal completion messages may bestored in a user's device and one or more of the messages may berandomly or progressively selected for display upon goal completion.

In another example, warning messages, if generated, may always bedisplayed first upon activating the information loop. Additionally oralternatively, regardless of the metric or message first displayed uponactivation of the information loop (e.g., from a sleep mode, deactivatedstate or other mode), an activity point indicator such as indicator 20may be illuminated to reflect a current goal progress as describedherein while the metric or message is displayed. The goal progressindicator may also be used to display goal progress whenever an activitypoint metric is displayed regardless of when the activity point metricis displayed. In other arrangements, warning messages may be displayedfirst without activation/use of the goal progress indicator. Instead,the goal progress indicator may be activated upon completion ofdisplaying warning messages and upon displaying a first metric.

FIG. 56 illustrates an example interfaces for displaying distanceinformation.

FIGS. 57A and 57B illustrate example battery level indicator displaysfor a wearable device assembly. In FIG. 57A, for example, the displaymay include only a battery image or may include a battery image or iconand a number representing an amount of charge (e.g., percentagecharged).

In another example, FIG. 57B illustrates interfaces 5711, 5713, 5715 and5717 displaying a battery icon in various states. Interface 5711illustrates the battery icon when a low charge is held (e.g., 10%, 15%,5%, etc.). As the device charges, lighting elements of the display mayilluminate from bottom to top and from right to left in that order.Accordingly, as shown in interface 5713, the bottom lighting element(not including the lighting element forming the battery border) to theimmediate left of the currently illuminated battery column isilluminated. In some examples, the lighting element corresponding to acurrent charging level (e.g., 26%, 35%, etc.) may be displayed as aflashing or blinking element o indicate that the device is stillcharging to that level. Interface 5715 illustrates the battery icon whenthe device is almost completely charged while interface 5717 illustratesthe battery icon when the device is completely charged.

When a device reaches low power (e.g., a specified range of power suchas 3-10% or 3-20%), the information loop may inject a “low battery”animation. In this low power range, there might be no change in metricgeneration and no change in data storage. However, if the battery powerreaches another threshold or level such as lower than 3%, the display(e.g., information loop) may stop generating metrics and the device maystop storing data (e.g., accelerometer data samples). Additionally oralternatively, in this further lower power range (lower than 3%), theradio connection may be closed and the network processor may also beshut down. Moreover, various information and displays may no longer beaccessible other than one or more predefined images when the lower powerrange is reached. For example, the display might only show a “plug”animation indicating the need for charging whenever user input isreceived. If the device is charged above the 3% level, then upon USB orpower unplug, the network processor may be reactivated, metricgeneration may continue, and samples may again be stored. The displaymay further show the full information loop (with any appropriatewarnings). If the battery is completely drained (e.g., 0% power), timemay be reset. Upon recharging, the device may require the user toconnect again to a setup or configuration software to reinitialize thedevice. For example, the device might only display a “SYNC” messageindicating a need to connect to a configuration program and/or device.

According to some arrangements, the device may further be configured todisplay reminders to the user. These reminders may include reminders toregister the device and/or to synchronize data. The reminders may betriggered by specified rules. For example, the registration reminder maybe triggered if the user has not registered the device and the reminderhas not been shown for a particular period of time (e.g., last 30minutes, last hour, last day, last week, etc.) and/or for a particularnumber of user interactions with or for a particular number of statechanges of the device (e.g., last 5 button presses, last 10 transitionsfrom a sleep state, etc.). A registration/synchronization remindermessage may include identification of the network address where the usermay register and/or synchronize his or her wearable athletic device. Ifa message (reminder or otherwise) is too wide or too tall to bedisplayed simultaneously on the device display, the message may bescrolled in a specified direction so that all information is displayed.Text may also be used to convey other metrics, type of metrics and/orunits of measurement such as calories burned, steps taken, activitypoints earned and the like.

FIG. 58 illustrates an example process flow for an action loop that maybe activated on a device. In addition to the device checks 5801 that maybe performed on the device upon wake up (e.g., transition out of a sleepmode), the device may further perform a battery check, a memory checkand a link check. The link check may be used to confirm whether aconnection (wired or wireless) exists between the two devices forvarious purposes including synchronization, message notification and thelike. In one example, the device may determine whether a connection isstill active with another device to which the device was previouslyconnected. Once the link check has been completed, the device mayprogress through the action loop. According to one configuration, thedevice may continue to scroll through the action loop in response to afirst type of user interaction such as continuous depression of abutton. Releasing the button or a second type of user interaction maystop the loop from advancing and a press and release of the button or athird type of user interaction may activate or cancel/deactivate thecurrently displayed function or action.

Warning messages may also be provided at this time. For example, upon auser entering input to access the action loop, various checks may beperformed and corresponding warning messages displays, if necessary. Theuser may be required, during the action loop, to continuously provide atype of input such as a continuous button depression through the warningmessages to reach the first action option. However, warning messages maystill be scrolled to completion (e.g., without reaching the first actionoption or action loop) regardless of if the user releases the button orif the user provides another button press. In one example, if the userpreviously viewed the same warnings in an information display loop,those same warning messages might not be displayed again when the actionloop is accessed. However, new warnings (e.g., warnings not previouslypresented to the user) may still be displayed. Alternatively oradditionally, a user may be allowed to skip through warning messages byentering a particular type or pattern of input (e.g., two button presseswithin a short time of each other).

After the initial link check, the device may progress to a tag functionthat allows a user to tag a current time and/or location as part of theaction loop. Depending on whether a link was detected in the link checkprocess, the tag functionality may operate differently. For example, ifthe tag function is activated, the device may determine and record atime stamp and/or location stamp. The location stamp may be generatedbased on data received form a location determination system such as GPSin the device or from a separate device (e.g., a mobile communicationdevice). The device may then transfer the tags if the device has a linkwith the other device. If the link does not exist, the device might notattempt to transfer the tags to the other device. In some arrangements,the location stamp might only be available if the link to the otherdevice is active. For example, if the activity tracking device does notinclude a location determination mechanism, the activity tracking devicemay request location stamping by the other device. Accordingly, if alink to the other device does not exist or is not active, the activitytracking device might not provide location stamping functionality.

FIG. 58A illustrates another example action loop flow. In this exampleflow, various action elements may be removed such as tagging and linkingdepending on the functionalities desired by the user and/or capabilitiesof the device. For example, a user may wish to remove tagging andlinking from the device to reduce battery consumption. Other functionsdisplayed in the action loop may similarly be removed from the actionloop using various configuration tools and/or software. Options anddisplays may also be removed from the various information and actionloops or other display states/modes in response to a battery level. Forexample, if a battery level is below a threshold amount (e.g., 30%), thedevice may automatically remove some of the options and/or displays.Other threshold amounts may be used. The threshold may also beuser-configurable. Additionally, the functions that are removed atdifferent threshold battery levels may also be configured/selected bythe user.

FIGS. 59A-59D illustrate example tagging interfaces that may bedisplayed on an activity tracking device. FIG. 59A illustrates a tagfunctionality indicator that may be displayed as part of the actionloop. In FIG. 59B, the user may select the tag function in interface a.Subsequently, the interface may display the tag icon followed by a checkmark to indicate that a time and/or location stamp has been recorded asshown in interface b. If the device is connected to another device, theinterface may display an indication of a data transfer process. In oneexample, the device may blink the tag icon to indicate that a datatransfer is being attempted. If the data transfer is successful, theinterface may display the tag icon followed by two indicators (e.g.,check marks), one indicating the recordation of the time and/or locationstamp and the other indicating a successful transfer of the tag as shownin FIG. 59C. If, however, the data transfer is unsuccessful, theinterface may display the tag icon followed by a first indicatorspecifying whether the tag was recorded and a second symbol or indicator(e.g., an “X” symbol) indicating that the data transfer was unsuccessfulas shown in FIG. 59D. Other symbols, icons, text, images and the likemay be used to indicate successful or unsuccessful tagging and/ortransfer.

Referring again to FIG. 58, the action loop may progress from the tagfunction to an optional link functionality and from the linkfunctionality (or the tag function if the link function is not provided)to a pairing functionality. Both the link function and the pair functionmay allow a user to connect the activity tracking device to anotherdevice such as a mobile phone or a portable music player. The linkfunction may relate to a first type of wireless or wired connectionwhile the pair function may relate to a second type of wireless or wiredconnection. For example, the first type of connection may include aWi-Fi connection while the second type of connection may include aBLUETOOTH/BLUETOOTH LOW ENERGY connection. Other types of connectionsmay include infrared-based connections, ZIGBEE, other RF-basedconnections and the like. The display of the link and pair functions mayinclude a status indicator specifying whether the link or pairing,respectively, is currently active. As noted, in some arrangements, alink function might not be provided in the action loop.

In some examples, the activity monitoring device may further includenear-field communication (NFC) components such as RFID systems. Forexample, NFC components may allow the device to receive or provideinformation to other devices upon reaching a predefined proximity to theother devices. Such information may include activity informationincluding level of activity, points accumulated, calories burned,activity routes and the like, payment information such as credit cardinformation, bank routing information, check information and the like,contact information sharing and the like and/or combinations thereof. Inone example, the user may use his or her monitoring device to makepurchases, thus alleviating the use of the need to carry a wallet orother payment items. In another example, a user may use one device totransmit user profile information to another device. Accordingly, if auser purchases another monitoring device, the user may automaticallysupply user information such as height, weight, name, etc. to the newlypurchased device through near field communications. In another example,synchronization of data (or other types of data transfer) may beautomatically triggered when the two or more devices are within thepredefined proximity as set by the NFC components. In still anotherexample, data may be automatically transmitted to and/or from a gamingconsole upon the device entering a predefined proximity of the gamingconsole using NFC. NFC may also be used to open doors to a house or car,access an office, gym, open gym locks, start a vehicle, immobilize avehicle (e.g., when the device has moved beyond the predefinedproximity), log onto a computer and the like.

FIGS. 60A and 60B illustrate example interfaces in which a link functionicon is displayed with a status indicator. In FIG. 60A, for example, thestatus indicator indicates that the link is inactive. In FIG. 60B, onthe other hand, the status indicator specifies that the link is active.The link function icon may also change depending on whether the link isactive or inactive. For example, the link function icon may display twoicons representing two devices. If the link is active, the icons may bedisplayed and/or displayed with equal illumination/intensity. If thelink is inactive, however, one of the icons may be displayed with lessillumination or intensity or might not be displayed at all.

Upon activating the link function, the appearance of the link icon orsymbol may be modified to reflect an attempt to link the device. In oneexample, the status indicator may be removed from the interface and thelink icon or icons may begin to blink intermittently as shown in FIG.60C. The link attempt may last for a specified period of time (e.g., 12seconds). If the link is successful, the interface will display apositive link indicator as shown in interface of FIG. 60D. If the linkprocess is unsuccessful, on the other hand, the interface may display anegative link indicator as shown in interface b of FIG. 60D. If a linkis currently active, selecting or activating the link function may causethe link to be broken or deactivated.

The link functionality, in one or more examples, need not be provided asa user-selectable option in the action loop. Instead, the device mayautomatically attempt to establish a link with one or more devices upona first button press or other triggering event (e.g., during and/or inconjunction with the link check shown in FIG. 58). In one example, uponthe user selecting a button while the device is in a sleep mode, thedevice may automatically activate a link establishment function (similarto that described above), without requiring the user to manuallyinitiate the link process. Whether the link is automatically establishedor if the option is shown in the action loop as a user-selectable itemmay be configurable by the user.

FIG. 61A-61C illustrates example user interfaces for a pairingfunctionality. For example, the device may include BLUETOOTHcommunication capabilities (or other short range network capabilities)and thus, may connect with local devices. FIG. 61A illustrates a pairingfunction icon while FIGS. 61B and 61C illustrate successful andunsuccessful pairing processes, respectively. In one example, upondetecting a particular type of user interaction such as a short buttonpress, the device may initiate a pairing process to detect and attemptto connect to a compatible device. If the device is successful paired toanother device, the display may provide a successful pairing indicatorsuch as the checkmark shown in FIG. 61B. If, however, the pairing wasunsuccessful, the display may provide an unsuccessful pairing indicatorsuch as an X mark as shown in FIG. 61C.

Alternatively or additionally, the pairing function might only display astatus (e.g., success or failure) of the pairing after the pairingfunction is activated. Accordingly, a pairing status might not bedisplayed when a user only navigates to the function through the actionloop. The device may also be capable of being paired with multipledevices. If a user pairs another device when a maximum number of deviceshave already been paired, the first device that was paired may beremoved from memory (e.g., a first-in-first-out rule).

An airplane mode function might also be included in the action loop.FIGS. 62A and 62B illustrate an example toggling process for turning anairplane mode on or off. Airplane mode may refer to a setting in whichall wireless communication capabilities of the device are deactivated soas not to interfere with operations of an airplane. However, airplanemode may be used in any desired circumstance and is not limited toairplane environments. In FIG. 62A, the display may initially provide anindication of the current airplane mode setting (e.g., on or off). Uponactivating the function (e.g., via a specified type of user interactionsuch as a short button press), the airplane mode function may switch toa setting such as on, as shown in FIG. 62B. In the on setting, thedevice may automatically turn off all wireless communication componentsincluding the pairing and link modules of the device. In somearrangements, if airplane mode is activated, the pairing and linkfunctions may also be removed from the action loop, making themunavailable for selection and activation. Upon deactivating airplanemode, the pairing and link functions may be reinserted into the actionloop. This automatic removal and insertion may aid the user indetermining what actions or functions are allowed during airplane mode.In other arrangements, the activation or deactivation of airplane modemight not affect whether the pairing and link functions are displayed inthe action loop. If the user activates the link or pairing function,however, the airplane mode may be automatically toggled to off (e.g.,when the mode is set to on). Alternatively or additionally, an airplanemode indicator such as a blinking or static light on either the topdisplay or the side display or both may be illuminated.

FIG. 63A-63D illustrate an example series of user interfaces that may bedisplayed for a reset function. The reset function may be used to erasethe memory of the device and/or reset all settings on the device (e.g.,goals, calibrations, initial activity measurements, etc.). In FIG. 63A,for example, a reset icon, animation, symbol, text or the like may beinitially displayed upon the action loop reaching the reset function.Upon activation (e.g., in response to a short press of a button or othertype of specified user interaction), the device may display a warning orconfirmation that the device is about to initiate a reset function. In aparticular example, as illustrated in FIG. 63B, the device may blink thereset icon, animation, symbol or text for a specified amount of time(e.g., 4 seconds, 5 seconds, 10 seconds, 1 second, etc.). During thiswarning or confirmation time period, the user may be allowed todeactivate or cancel the reset function by providing a specified type ofuser interaction such as a short button press. Other types of warning orconfirmation messages, animations, audio, haptic feedback and the likemay be used. If the user does not cancel the reset request, the devicemay begin the reset process at the end of the warning or confirmationperiod. Cancelling the reset request may include a user interacting withthe device in a specified manner such a short press of a button (e.g., abutton press having a duration less than specified threshold duration),a long press of a button (e.g., a button press of at least 2 seconds, 3seconds, 10 seconds, etc.), movement of the device and the like. In aparticular example, cancelling the reset request may correspond to thesame type of user interaction as activating the reset function.

If the reset request is not cancelled within the warning or confirmationperiod, the device may initiate the reset process. FIG. 63C illustratesan example display that may be used to convey the progress of aresetting process. For example, the reset icon, animation, symbol ortext may animate in some fashion such as illuminating clockwise untilthe reset process is complete. Once the reset process is complete, acompletion indicator (e.g., a logo) may be displayed on the device asshown in FIG. 63D. The completion indicator may include a variety ofimages, symbols, text, icons and the like and may include both staticand animated indicators. As noted herein, different types of user inputor user interaction may correspond to different commands, functions,actions and the like.

If the action loop is activated or otherwise accessed from theinformation loop, the action loop may time out to a most recently viewedmetric in the information loop. For example, if a user transition froman activity point metric display in the information loop to the actionloop and subsequently allows the action loop to time-out (e.g., no userinteraction for a specified amount of time), the device may display theactivity point metric after exiting the action loop and prior toentering the time-out state (e.g., deactivation of the display).

In one arrangement, a wearable device might only have a single userinput device to minimize complexity. The user input device may include abutton, a scroll wheel, a touch sensitive input device, a joystick, atrackball and the like. In such cases, different types of interactionwith the input device may correspond to different actions such asactivating and scrolling through the action loop, activating andscrolling through an information loop, toggling functions on and off,activating various functions and the like. For example, depression ofthe button for different durations or holding the button down may invokedifferent actions and functions. In another example, patterns of buttondepressions may also be used to differentiate between actions andfunctions. In the example of a touch sensitive input device, differentgestures or types of motions may correspond to different actions. In aparticular example, a user may contact the touch sensitive input devicewith a single finger to activate an action loop and two fingers(simultaneously or substantially simultaneously) to activate aninformation loop.

According to one or more aspects, a user may pair his or her wearabledevice with another user's wearable device through wireless connections.In one example, the wearable device may both pair with devices andwirelessly link with devices. The pairing function may, in a particularexample, specifically relate to BLUETOOTH pairing and connections whilelinking may refer to Wi-Fi or other types of wired or wirelessconnections. In other examples, the pairing function may relate to afirst type of connection while linking may refer to a second type ofconnection different from the first type. For example, other connectiontypes may include infrared and RFID.

When a user is within a predefined proximity to another user, the user'swearable device may detect the wearable device of the other user. Thefirst user may then add the second user as a friend by initiating asearch process through the first user's wearable device (e.g., BLUETOOTHsignal detection). Data such as contact information or identification ofthe friend may then be transferred from the second user's device to thefirst user's device (e.g., through wired or wireless connections). Thecontact information or identification that is transferred betweendevices may be configurable such that a user may specify the type andcontent of the contact information or identification that is transmittedto the other device and user. Friend information may be added to thefirst user's account upon the first user synchronizing his or herwearable device to an athletic performance monitoring service or site.In one or more arrangements, confirmation may be required from the otheruser or friend before any data transfer is allowed or executed. In someexamples, the identification of another device user may correspond to aregistered user identifier with a social network or other communitysite. Accordingly, a user may receive a FACEBOOK username or identifierfrom another user's device for identification purposes. The device maythen store the other user's FACEBOOK username or identifier as a friendin the device and/or in an account of an athletic activity trackingservice.

The addition of a friend through pairing of devices may further cause ortrigger the establishment of a relationship between the two users on acommunity site. In the above example in which FACEBOOK usernames areused as identifiers, the device, upon connecting to a network, maytrigger generation and transmission of a relationship request to theother user through FACEBOOK. Accordingly, a relationship such as“friends” or “workout partners” may be established on the community siteupon the other user accepting the request or upon detecting mutualrequests being generated and sent.

FIG. 64 illustrates example processes and interfaces for adding a friendthrough a user's wearable device. For example, a user may initiallydepress an interactive button for a predefined amount of time toactivate a friend search function. Upon finding a friend, a “+FRND”message may be displayed and edge indicator lights may be illuminated toindicate a progress of data transfer. As noted above, transferred datamay include name, e-mail address, other contact information, user ID andthe like. This data may later be used to add the friend to a user'saccount on an athletic performance monitoring site.

According to another aspect, a user may define and/or store geographiclocations in the device. This may allow a wearable device to identify(or assume) a type of activity being performed (e.g., a park locationmay correspond to a running activity while a ski resort may correspondto a skiing). FIG. 65 illustrates example interfaces which may beprovided for determining the user's location if the location has beenpredefined. For example, upon the user's wearable device detecting theuser's location, the wearable device may determine whether this locationis known (e.g., stored in the device or another database). Identifying alocation may be performed based on latitude and longitude, an areaaround a set of coordinates, a particular address or area around aparticular address and/or combinations thereof. The location informationmay be determined by the device or based on information received from aconnected device such as a mobile communication device or portable musicplayer with location determination components (e.g., GPS, cellulartriangulation, etc.). If location information is received from anotherdevice, the location information may specify the location of the otherdevice. The location of the other device may then be used to tag theactivity or a location of the user or wearable device may be determinedbased on a known or approximated distance between the wearable deviceand the other device.

In some examples, a user may manually specify a location (e.g., byentering a zip code, address, etc.) through the device. If a predefinedand stored location is found, the corresponding name or label may bedisplayed for the user's information. The name or label may be definedautomatically from a network database or may be manually entered anddefined by a user. The network database may comprise informationretrieved from search engines, for instance, and/or may include locationinformation defined by friends or other users of the service. In someexamples, the wearable device my initially determine whether thelocation is a known stored location by querying its own storage system.If the location is not a known stored location within the wearabledevice, the device may query a network database or a database of aconnected device to determine whether the location is known.

FIG. 66 illustrates a process by which a location determination systemmay be used to track a user's location. The location information may bestored with the athletic data for a particular athletic activitysession. In one example, upon a user initiating a workout or athleticsession, a position determination system and function (e.g., usingGlobal Positioning Systems) may be automatically triggered. The positiondetermination system may be provided by the wearable device or on aseparate device such as a mobile communication device. In one example,the wearable device may be communicatively linked to the separatelocation determination device/system. In either case, a locationdetermination application may begin pinging or detecting the device'slocation. If the user's location has changed, the application may logthe new location and wait a predefined amount of time before detectingthe device's location again. For example, the application may wait 10seconds, 15 seconds, 30 seconds, 1 minute, 5 minutes, etc. beforerequesting the device's location. If, however, the device's location hasnot changed, the application may wait a predefined amount of time beforedetecting the device's location again. The wait time may increaselogarithmically, incrementally, exponentially or might not increase atall for each successive time the device's location has not changed.

In situations where the location determination is performed on aseparate mobile communication device, the application may automaticallyassociate athletic data received from the wearable device with thelocation information detected by the location determination system. Forexample, the location data may be stored as metadata or other types ofattributes for the athletic data.

To encourage athletic performance, users may compete with one another.For example, a user may compete with another user to see which user canaccumulate the most activity points, calories burned, miles run or thelike in a day or other predefined time frame.

Activity points may be accumulated based on a user's physical movementor activity during the period of time. For example 1 point may be earnedfor every 20 calories burned. In another example, 1 point may be earnedfor every 0.25 mile run. Various types of conversion factors may beused. In other arrangements, the competition measure may be the activitymetric (e.g., miles, calories, heart rate, etc.). In such cases, othertypes of activities that are not measured according to the athleticstatistic may need to be converted prior to being counted towards thetotal or might not be counted toward the competition. The competitiontotal/progress may be separate from an overall activity progress and maybe stored separately as well.

FIG. 67 illustrates an example interface on a wearable device forindicating a current status of a competition between two users. Theprogress may be conveyed through a message such as “v Lisa: YOU+425,”which may indicate that the competition is against another user namedLisa and that the present user is ahead of Lisa by 425 points orcalories or other metric. The competitor data (e.g., an amount ofcalories burned, a number of activity points earned, etc.) may besynchronized through a remote network system and/or directly between theuser's wearable devices. In another example, one or more of the user'swearable devices may synchronize data with the other user through alocal communication device connected in a wired or wireless manner orother intermediary devices.

In one or more arrangements, the relative positions of the two users maybe indicated on the edge illumination as well. FIGS. 68 and 69illustrate examples of competition status indication using edge lights(e.g., a side display) of a wearable device. For example, illuminationof an edge light toward the right may indicate that the user is behind(as shown in FIG. 68) while illumination of an edge light toward theleft may indicate that the user is behind (as shown in FIG. 69). Anequilibrium or equal point (e.g., where the users' progress issubstantially equal to one another) may be defined anywhere along theside display. In one example, the distance of an illuminated light froma center point of the set of edge lights may represent a degree by whichthe user is ahead or behind. Other displays or the wearable device maysimilarly display such information. For example, a top LED matrixdisplay of the wearable device may similarly convey a competition statusbetween two or more individuals.

FIG. 70 illustrates another series of example user device interfaces forindicating a game or competition status between the wearer and one ormore other users. As with other messages, the competition status messagemay scroll if it is too large to display at one time on the displayinterface. Alternatively or additionally, if a message, image or otherinformation is too large to be displayed all at once on a singledisplay, multiple displays may be used. For example, if a message is tootall for a top display of a wearable device, the additional portions maybe displayed on the side display of the wearable device.

FIG. 71 illustrates an example interface message that may be displayedupon identifying or adding a new opponent. For example, the name of thenew opponent may be displayed. A user may be required to confirm thatthe detected or identified new opponent is the desired opponent bydepressing the interactive button for a predefined amount of time.

FIG. 72 illustrates an example registration process flow in which a usermay be instructed to initially plug-in the device, download the softwareand pair the device with the device through which registration will beperformed (e.g., a network-connected device). Once connected, the usermay then enter registration information to define a service profile foran athletic performance monitoring service. The profile may then bestored at activity monitoring service and provided to the wearabledevice for storage as well. If a user exits the registration processprior to completion, the device may use default settings.

In some arrangements, an application may be downloaded to one or morecomputing devices to facilitate and/or enhance the tracking of activitydata. For example, the application may enable graphing of activityinformation and display of such graphs as well as providingrecommendations for improvements and setting of goals. The applicationmay further facilitate configuration and updating of the device as wellas communication between the device and a remote site such as anactivity monitoring service/site. Additionally or alternatively, thewearable device may be locked from use (e.g., all functionality beyondregistration disabled, all functionality but normal athletic performancemonitoring disabled) prior to registration. Normal activity performancemonitoring may include sensing of activity by a user, display of thatinformation on the display interface and/or tracking of goals. However,no data may be stored and no association between the user and the datamay be established. In some examples, some data such as activityinformation may be stored in the device or the application during aninitial phase, startup and/or registration.

FIGS. 73A-73G illustrate example registration interfaces that may beused to register a new user and/or device through the Internet or othernetwork.

FIG. 74A illustrates another example registration process flow in whicha user may register with the device and the user through a mobileapplication. In contrast to the process flow of FIG. 72, theregistration of FIG. 74A is performed through an application executingon a mobile communication device while in FIG. 72, the registration isperformed through a website or other software (e.g., software executingon a desktop or stationary computing device).

FIGS. 74B-74P illustrate example registration interfaces that may beused to register a new user and/or device through an application on amobile communication device.

Upon successful registration, the wearable device and the applicationthe mobile communication device may provide indications that the deviceand application are ready to begin tracking activity. For example, FIG.75 illustrates an example user interface display on a wearable deviceincluding a message greeting the user. The greeting may indicate thatthe device is ready to begin tracking activity. Other indications mayalso be used.

In FIGS. 76 and 77, the application may provide a message that thewearable device is ready for tracking activity and further provideinformation regarding the capabilities of the application in trackingactivity, respectively. For example, while the device may measure andrecord various metrics including activity points, calories burned,distance run and the like, the application may be configured to processthe measured and recorded data to provide additional informationincluding location/route information, progress/trend information andcomparison data (e.g., comparing the user's activity with friends orother users).

FIGS. 78A-78G illustrate example user interfaces for registering a newdevice for an existing user. For example, registration of a new devicefor an existing user may require the user to enter login credentials.The user may then link the new device upon successful authorization.

Other types of registration processes may also be used including thosewith more or less options as desired by an activity tracking serviceand/or the user. In some examples, portions of the registration processmay be optional (e.g., setting a daily goal, display setup, etc.).

According to one or more aspects, a user may login or sign on to anactivity tracking service or application using a variety of differentaccounts including accounts not provided by the activity trackingservice. FIG. 79, for example, illustrates an application display on amobile device that provides sign in options using different accountsincluding an activity tracking service account, a FACEBOOK account and aTWITTER account. In one or more examples, the activity tracking servicemay correspond to a provider of the activity tracking application. Tosign in or register with the activity tracking service using externalaccounts such as a FACEBOOK or TWITTER account, the user may be requiredto authorize transmission of data and/or other interactions between theactivity tracking service and the external system or site.

FIGS. 80 and 81 illustrate example user interfaces for providingauthorization for the activity tracking site to communicate data witheach of the external services.

FIG. 80, for instance, illustrates a FACEBOOK login page requiring theuser to enter login information to link the activity tracking service tothe user's FACEBOOK account. FIG. 81, on the other hand, illustrates aTWITTER login that may require the user to login to authorize anactivity tracking service or application to interact with the user'sTWITTER account. As shown in FIG. 81, the user may be advised of theapplication or service that would be authorized as well as thefunctions, data, interfaces of the external service that would be madeavailable to the application or service receiving authorization.

Once a user has logged into the activity tracking service orapplication, the user may be presented with profile information asillustrated in FIGS. 82A and 82B. The application interface 8200 mayinclude a profile picture 8201, an activity gauge 8203, identificationof a device used 8205 and other metrics including a daily activityaverage and a number of active days. The identification of an activitytracking device used 8205 may correspond to the device used to measureand record activity and may include a listing of multiple devices if theuser's activity is tracked using multiple different devices. In someinstances, only one of the multiple devices may be identified ininterface 8200. For example, the device with which a majority of theuser's activity is tracked may be displayed without identifying otherdevices. In other examples, a user may select a device to be identifiedin the device identification 8205.

In section 8207, recent activity may be displayed. Activity may begrouped by time periods such as days, weeks, months, hours, two hours, 6hours, 12 hours and the like. Accordingly, the recent activity section8207 may display a most recent number of activity periods. In aparticular example, section 8207 may display the most recent 3 days ofactivity, each day being listed as an entry in section 8207. Section8209 may be used to display records that have been achieved by the user.Records section 8209 may include multiple predefined record categoriessuch as best day, best week, best month, best day of week, longeststreak and the like. Selecting one of the categories may cause theapplication to display the corresponding record for that category. Inaddition to recent activity and records, the interface 8200 may furtherinclude a trophy section 8211 configured to display awards andachievements of the user. For example, various trophies and milestonesmay be defined such as reaching a certain number of activity points inone day, achieving a streak of days in which the individual has reachedan activity point goal, exceeding a goal by a specified amount and thelike.

A function bar or toolbar 8213 may be displayed in interface 8200 toallow a user to switch between various top level modes of theapplication. For example, selecting the “Me” tab in bar 8213 may displaythe profile information as shown in FIGS. 82A and 82B. Selecting the“Home” tab, on the other hand, may cause a visual display of a currentlevel of activity for a current session or time period to be displayed.In one example, the “Home” tab may cause an activity point tracker to bedisplayed during an evaluation period. The evaluation period, asdescribed, may, in some instances, correspond to a first 24 hours ofusing the device.

Alternatively or additionally, the Home, Activity and Me modes orinterfaces may be displayed as a drop down menu or other type of menuthat is displayed upon user selection of a menu option as illustrated inFIG. 82C. By hiding the Home, Activity and Me mode options, the displaymay provide more real estate to other visual items. In contrast to theinterfaces of FIGS. 82A and 82B, the interface of FIG. 82C may requirean additional user input or interaction prior to selecting one of thegeneral sections of the application.

According to another arrangement illustrated in FIG. 82D, a profileinterface may further include a menu for additional functions of theapplication. In one example, menu 8221 may be displayed upon receiving auser interaction different from a user interaction configured to triggera general mode selection menu as shown in FIG. 82C. In menu 8221, forexample, the user may be presented with options such as synchronization(e.g., with a wearable activity tracking device), view notifications,settings and share. The options included in menu 8221 may changedepending on the current active interface, information display or modeof the application.

FIGS. 83A-83D illustrate examples interfaces displaying an accumulatedamount of activity points during an evaluation period. The activitytracking interface 8300 may include a variety of indicators including anactivity point indicator 8301, a graphic evaluation time remainingindicator 8303, a textual evaluation time remaining indicator 8305, anda message portion 8307 that may convey a variety of informationincluding a level of progress. The graphical time remaining indicator8303 may include a circular track that progressively changes appearance(e.g., fills in in a specified color or appearance) as the evaluationtime period counts down. A textual/numerical time indicator 8305 mayalso be displayed to provide detailed time accounting. Various othergraphical indicators may be used to indicate an amount of time completedand/or an amount of time left in the evaluation period. The activitypoint indicator 8301 may provide the user with information as to anumber of activity points that he or she has accumulated. Activity pointindicator 8301 may be updated in real-time, substantially in real-time,on-demand, periodically, aperiodically and/or based on other specifiedschedules or rules. Updating may include synchronizing data with thewearable device. In one or more examples, updating of the activity pointcount may be triggered by movement of the mobile device or transitioningfrom a sleep state to an active or idle state. Additionally oralternatively, update indicator 8309 may be used to identify when datais being synchronized or otherwise updated to the mobile applicationfrom the wearable device. In some arrangements, an option (not shown)may be provided to request updating or synchronization of the activitypoint data.

FIGS. 83E-83H illustrate an example synchronization/update functionalitythat may be activated on the mobile application by performing apredefined gesture in the interface. For example, the user may update orsynchronize data from the monitoring device to the mobile communicationdevice by pulling the user interface down using touch input andreleasing. Other various types of user inputs and commands may also bedefined for activating an update functionality. Accordingly, theactivity data may be both updated automatically at predefined times orcontinuously and/or in response to a manual command from the user. Inyet other examples, other triggers may be used to activate updating andsynchronization. In one particular example, activation of the mobilecommunication device display (e.g., from a power save state), activatingthe activity tracking and monitoring activity, viewing a particularinterface in the application and the like and/or combinations thereofmay trigger updating. The interfaces shown in FIGS. 83E-83H correspondto non-evaluation modes such as an activity tracking mode, a summarymode and a profile mode, respectively, however, updating activity datamay be performed in similar fashion during evaluation modes as well. Insome examples, as shown in FIGS. 83F-83H, the interface may alsoindicate to the user the last time data was updated to the mobileapplication.

Referring again to FIG. 83A, message portion 8307 may be used to conveycontextual information. For example, during the beginning of anevaluation period, the message portion 8307 may indicate that thewearable device is in a preliminary phase of evaluating the user (asshown in FIGS. 83A and 83B). As the evaluation period progresses, themessage may change to indicate that the user has completed half of theevaluation period, as illustrated in FIG. 83C. When the user is close tocompleting the evaluation period (e.g., within 5%, 10%, 15%, 25%, etc.),the message portion 8307 may indicate such a status to the user, asshown in FIG. 83D.

In some instances, the mobile device executing the activity trackingapplication may enter an idle state (e.g., the display is turned off anda key lock or input lock is initiated). When the device enters the idlestate, notifications using the underlying operating system of the mobiledevice may be generated and displayed. The notifications may indicate aprogress toward completion of the evaluation period even when theapplication is not active or the device is not actively displaying theactivity tracking application.

FIGS. 84A-84C illustrate a set of example notification interfaces thatmay be displayed at various times during the evaluation period. Thenotifications may, in some arrangements, be displayed on top of a touchinput lock screen. Accordingly, the user may still interact with thenotification but may be restricted from interacting with any otheraspects of the device interface until the input lock is deactivated.Such notifications may also be generated and displayed when theapplication is executing in a background (e.g., not displayed orexecuted in a foreground of the operating system). Thus, if the user ischecking e-mail or listening to music through other applications, theactivity point tracking notifications may still be displayed even whenthe activity point tracking application is not in the foreground orbeing actively displayed.

FIGS. 84D-84F illustrate another set of example notification interfacesthat may be provided to the user upon detecting various triggeringevents. The notifications shown in FIGS. 84D-84F may be provided in adrop down menu, where an initial notification indicator is displayed ina header margin of the interface. The activity tracking notificationsmay be displayed along with notifications from other applications or maybe displayed separately from other notifications. The notificationsystem may be provided by the underlying operating system and invoked bythe activity tracking application (e.g., running in the background).

Upon completion of the evaluation period, the application may display acompletion message as shown in FIG. 85A. In addition to amount ofactivity point accumulated during the evaluation period, the applicationmay further display an option to synchronize the activity data from thewearable activity tracking device. In some instances, the activity pointamount tracked in the application may be up to date as of the mostrecent synchronization. Accordingly, the activity data may be up to dateif the data is continuously synchronized or synchronized in real-time.In some instances, the activity point amount displayed might not beaccurate depending on when the most recent update or synchronization wasperformed. Accordingly, upon selecting the synchronization option 8503,additional or different data may be received from the wearable device.

The synchronization process may include a synchronization interface 8510configured to display a progress bar 8511 as shown in FIG. 85B alongwith a running total of the activity points as the synchronizationprogresses. For example, the number of activity points display may beanimated (e.g., counting up) as additional activity point data isreceived from the wearable device. The synchronization interface 8510may further indicate an amount of time remaining in the synchronizationprocess (e.g., via progress bar 8513).

Once the evaluation period has been completed and the evaluation periodactivity data has been synchronized with the application and mobiledevice, the application may provide more detailed information regardingthe user's activity during the evaluation period. For example, theuser's activity may be displayed with more granularity and withadditional analysis.

FIG. 86 illustrates an example interface providing a summary of theactivity performed during the evaluation time period. For example, theapplication may determine and identify a period of highest activity aswell as a percentage of the time period during which the user wasactive. The summary may further compare the user's performance with anaverage for other users. In some arrangements, the average may be anaverage for users of a particular type. For example, the average may bethe average for all males, for all users ages 18-25, for all usersliving in a particular state, zip code, region, etc., for all usersusing a particular activity tracking device, for all users of aparticular height or weight and/or combinations thereof.

FIGS. 87A and 87B illustrate other example information displays forviewing and analyzing evaluation period activity data. In FIG. 87A, asummary 8701 of the amount of activity points, a number of caloriesburned and the number of steps taken may be conveyed. Other metrics mayalso be included as needed or desired and may be configurable by theuser, by an activity tracking service or another entity. The display ofFIG. 87A may further include an option 8703 to display additionalinformation or details regarding activity performed during theevaluation period.

Upon selection of the additional information option, a more detailedview of the evaluation period activity may be displayed as illustratedin FIG. 87B. For example, a graph 8711 of the user's activity level overtime may be displayed to help the user identify particular times of highor low activity. Additionally, analytical information may be displayedincluding a most active hour, a percentage of the day (or otherevaluation time period) that the user was active and a comparison of theuser's activity points versus an average user's activity points duringthe same time period. Being active may be defined as any amount ofmovement detected and recorded by the wearable device. In otherexamples, activity or being active may be defined based on a thresholdlevel of movement or activity detected. For example, if activity ormovement is detected based on steps, the user may be required to performat least 2 steps within 5 seconds for those 5 seconds to be registeredas active time. In other examples, the movement detected by the wearabledevice may register as a signal having an amplitude or magnitude. Insuch cases, the wearable device might only record signals having atleast a threshold amplitude or magnitude. Thus, a user might only beconsidered to be active upon exhibiting movement of a thresholdamplitude or magnitude.

From the detailed information display, the user may select a goalsetting option 8713. The goal may correspond to a specified amount oftime such as a day, an hour, a week, a month or the like. In somearrangements, the goal time period may correspond to the evaluation timeperiod. For example, if the evaluation time period was 1 day, the goaltime period may be defined as 1 day. Alternatively, the user may definehis or her own goal time period.

Upon selection of the goal setting option 8713 (FIG. 87B), theapplication may further display a goal setting menu 8801 as shown inFIG. 88A. In the goal setting menu 8801, the user may be provided withmultiple predefined options for setting the goal. The predefined optionsmay be generated based on the activity data recorded during theevaluation time period. For example, the options may include exceedingthe activity recorded during the evaluation time period by a specifiedamount or percentage, setting the goal to be equal to the activityrecorded during the evaluation time period, or setting the goal to be aspecified amount or percentage less than the activity recorded duringthe evaluation time period. The goal may be defined by any of themetrics measured and recorded by the wearable device including activitypoints, calories burned, steps performed and the like. In somearrangements, different goals may be specified for each of the differentmetrics. For example, a user may specify that he or she wishes to reach1200 activity points and burn 700 calories. In another example, a usermay set goals to achieve 1500 activity points and perform 15000 steps.

After the user has selected one of the predefined goals, the user mayhave the option to fine tune the goal. FIG. 88B illustrates an examplegoal tuning interface that may be displayed upon a user selecting a goalfrom the goal menu 8801 (FIG. 88A). In FIG. 88B, the user may slider bar8803 to adjust the predefined goal. The slider bar 8803 might only allowthe user to decrease or increase the predefined goal by a specifiedamount or percentage. In other arrangements, the user's ability todecrease or increase the predefined goal may be unrestricted. Oncefinalized, the user may then save the goal by selection option 8805. Thegoal may then be set for the goal time period. The goal time period maystart immediately or may start at a future time (e.g., the next day, atime selected by the user, upon detecting a triggering event and thelike). A triggering event may include a user selecting a button on thewearable device to start the goal time period, detection of sustainedactivity for greater than a specified amount of time (e.g., 5 minutes,30 seconds, 1 minute, 1 hour, 30 minutes, 10 minutes, etc.), and thelike and/or combinations thereof.

Activity may be tracked based on a specified goal or independently of agoal. In instances where activity is tracked based on a goal, the usermay view his or her current progress in a variety of ways. As discussedherein, the activity tracking application may include a profileinterface, an activity view interface and a home interface. Each ofthese interfaces may provide information relating to the user's currentprogress toward a goal and an amount of activity performed. Thedifferent interfaces may provide different levels of detail, differentmetrics, different activity data analyses, different types of additionalinformation displayed with the current progress information and thelike.

FIG. 142 illustrates a notification message that may be generated andprovided to the user upon detection that a first full goal period hasstarted. For example, if a goal period corresponds to a day (24 hours),the application may generate a notification message when the first fullday (e.g., after application installation, device registration, etc.)has begun. The start of a day or a goal period may be defined by theuser or set by default. In one example, the start of a day or 24 hourperiod may be defined as 8 AM or in other instances, may be defined asmidnight. Accordingly, upon reaching the start time, the user may benotified. In some examples, the interface of FIG. 142 may be providedwhen an evaluation period is not used or required. Thus, instead ofinitiating an evaluation period, the user may begin a goal trackingsession once the user has downloaded the application and completed anyrequired setup.

FIG. 89A illustrates an example home interface in which an accumulated(e.g., earned or detected) amount of activity points is tracked inrelation to a goal. In a particular example, the goal may be a dailyactivity point goal. The goal may be visualized as a shape or object8901 having a transparent or semi-transparent appearance. As the useraccumulates activity points, the shape or object 8901 may begin tochange appearance. For example, one or more portions of the shape may bemodified to display colors. In some instances, the portions of theobject that are modified may correspond to a progress bar or indicatorsuch as indicator 8903. The amount of the shape that is modified maycorrespond to an amount or percentage of the goal that has beencompleted. Accordingly, if the user has completed 25% of the goal, thegoal shape may be 25% colored in and 75% transparent. Other visualeffects or visual indicators may be used to differentiate between anamount of a goal still to be achieved and an amount of the goal alreadycompleted.

The visual indication of the goal amount completed such as progressbar/indicator 8903 may also include patterns, colors or other visualeffects that represent a distance from the goal. For example, red mayrepresent minimal progress towards the goal (e.g., 0-10% progress),while yellow may represent moderate progress (e.g., 40-60% progress).Green may represent significant progress (e.g., 80%+ progress). Othercolors may be used to represent the other progress levels (e.g.,percentages). In the examples illustrated in FIG. 89A, the goal progressspectrum may be represented by a color spectrum (e.g., range of colorsfrom red to green). In some arrangements, the progress bar may bedisplayed in a single color, where the color may depend on the amount ofthe goal achieved (e.g., green when the user has achieved at least 75%of the goal, red if the user has achieved less than 15% of the goal,etc.). In other arrangements, as in FIG. 89A, the progress bar orindicator 8903 may be displayed in multiple colors, where each of thecolors represents a level of progress associated to a correspondingsection of the shape 8901 and progress indicator 8903.

Additionally, various other metrics and progress information may bedisplayed in the interface including calories burned, amount of time theindividual has been active, a number of steps taken and/or a distancetraveled. The application may also provide various messages to the userincluding motivational messages, instructional messages (to improveactivity level), information messages (e.g., a number of activity pointsneeded to complete the goal), trivia information and the like. Themetrics may be determined (e.g., calculated) by the application ordevice on which the application is executing and/or by the wearableactivity monitoring device. Similarly, messages may be generated orselected by the application or by the wearable activity monitoringdevice.

FIG. 89B illustrates an example activity interface that may displayother and/or additional types of activity information. Instead of or inadditional to display goal information, interface 8920 may displayactivity summary information that reports user activity for a day, aweek, a month, a year, and/or other predefined or customized timeperiods. In the summary interface 8920, the user's activity may bedivided into predefined time periods such as days, hours, weeks, months,years, etc. In one example, the predefined time periods may depend onthe view that is selected. In a particular example, if a day view isselected, the user's activity may be divided into hours while if theweek view is selected (as shown in interface 8920), the user's activitymay be broken down by day.

The user's activity level may be visualized in a variety of mannersincluding using graphs such as bar graph 8921. Each day of the week maybe represented by an activity bar in graph 8921 and each bar may becolor-coded to represent a level of goal completion. For example, if auser completed a daily goal on one or more days, the bars correspondingto those one or more days may be displayed in a first color such asgreen. However, if a user failed to reach a first threshold amount ofthe goal (e.g., 25%), the corresponding bar may be displayed in anothercolor such as red. If a user reached the first threshold but failed toreach a second threshold, the corresponding bar may be displayed in yetanother color such as yellow. Any number of thresholds may be definedand any number of colors may be used. In a particular example,thresholds for exceeding the goal may also be defined and may berepresented by a color or pattern or visual effect. For example, if auser exceeds a goal by a specified amount (e.g., 10%), the activity barmay be displayed with flames or in black. If the user exceeds the goalby an even greater amount (e.g., 25%), the activity bar may be displayedas an ice block, for instance. Other visual, textual or image-basedindicators may be used to indicate a level of completion of acorresponding goal, including icons, animations, patterns, levels oftransparency and the like and/or combinations thereof.

Summary section 8923 may further display a total amount of activitypoints earned by the user for the time period displayed (e.g., a week).Additionally, the interface 8920 may indicate a number of goals thatwere reached. In the illustrated example, the user completed 4 of 7daily goals. Interface 8920 may further provide a user with the abilityto select one or more of the activity bars to view more detailedinformation about that day including a number of activity points earnedon that day, the goal set for the day and the like. Additionally oralternatively, interface 8920 may also display various metrics for thetime period displayed.

FIG. 89C illustrates another example interface in which activity pointinformation may be displayed. In particular, interface 8930 may includea display of a user's profile including a total amount of activityaccumulated (e.g., for all time), averages, a number of activity timerperiods (e.g., days, weeks, months, hours, etc.) as well as indicationsof recent activity and records as described herein. The user may selectany of these information items to view additional details. For example,selecting the best day record may display a graph of the user's activitylevel on that day on an hourly basis. The details may further include agoal that was defined for the day and statistics or metrics (e.g.,calories burned, distance moved, steps taken, average pace, etc.) of theactivity performed on that day.

According to one or more aspects, the activity tracking visualizationand interface may automatically change depending on an orientation ofthe displaying device. For example, if the displaying device is held ina profile orientation, the interface may appear as shown in FIG. 89A.However, in some instances, if the displaying device is switched to alandscape orientation, the interface may change to appear as shown inFIG. 89D. In FIG. 89D, the interface may provide a graph of activityearned over a specified unit of time such as per hour, per minute, persecond, etc. Accordingly, the landscape view may provide a further levelof detail regarding the activity point accumulation of the day or otheractivity tracking time period. The type of data or interface that isgenerated and displayed may depend on the dimensions of the displayincluding width and height in the current orientation. For example, agraph that is of a particular width might not be selected or displayedwhen the display is in an orientation having a width less than the widthof the graph. Additionally or alternatively, the view shown in FIG. 89Dmay be selectable in profile orientation as well. For example, the usermay select an option to view the hourly or minute-by-minute breakdown ofthe activity points earned regardless of the orientation of the displayor display device.

As described herein, a user may define a goal to which the user'sactivity is compared. Once a goal is set, in some arrangements, the usermay modify the goal or set another goal for the same time period oranother time period (e.g., the next day, a next week, the weekend,etc.). For example, during the course of a day or other time period, theuser may realize that he or she is on track to exceed the currently setgoal. Accordingly, the user may wish to modify the goal to a morechallenging setting. In another example, if a user realizes that he orshe is unlikely to complete a currently set goal, the user may modifythe goal to be less challenging. The user may also be allowed to setadditional goals without having to wait for a current goal or goal timeperiod to expire. For example, while resting during a first day ofactivity, the user may set a goal for the next day or an upcoming weekor the like.

FIG. 90A illustrates an example interface by which a user may activate agoal modification or setting function. The user may activate goal optionmenu 9001 by selecting a displayed option and/or by interacting with thedisplay device in a specified manner. For example, the user may berequired to depress a button for a predefined amount of time to activatethe goal option menu 9001. In another example, the user may activate thegoal option menu 9001 by entering a gesture on a touch sensitive displaydevice. The goal option menu 9001 may include an option for modifying acurrent goal or for setting a future goal. The device may automaticallyselect a time period for the future goal based on a first time periodfor which a goal has not been defined. For example, if a goal has beendefined for each of the next 2 days, the device and/or application maydefine the future goal option 9003 as being directed to the third day.In some arrangements, activity monitoring and tracking may be suspendedwhile the goal modification menu 9001 is active. In other arrangements,activity monitoring and tracking may continue even while the goalmodification menu 9001 is active.

Goals may also be modified to reflect different metrics. For example, ifa current goal is defined based on activity points, a user may modifythe goal to correspond to a number of calories burned or a number ofsteps taken. Additionally or alternatively, goal progress (e.g.,detected or accumulated activity data) may be reset upon setting of anew current goal. In other arrangements, if a user switches metrics fora current goal, the existing goal progress may be converted into the newmetric based on a specified conversion factor. In some configurations,activity may be detected and tracked (e.g., by the wearable deviceand/or by the mobile application device) using multiple metrics.Accordingly, the device may retrieve a different set of metrics if themetric for the goal is modified.

Goal modification and setting functionality on the mobile application,the activity tracking wearable device and/or an activity trackingservice might only be made available to users who have completed aninitial evaluation period. This requirement may allow the wearabledevice, the activity monitoring application and/or an activitymonitoring site to better tailor goal suggestions, products, coachingtips, and the like to the user prior to the user embarking on a goal.Additionally or alternatively, the evaluation period may allow thewearable device to provide more accurate measurements and tracking bycalibrating its sensors and algorithms for activity detection andmeasurement.

Upon selecting a goal modification or setting function, the user may beprovided with an interface for defining a goal. In one example, theinterface may appear similar to the goal setting/modification interfaceas shown in FIG. 88B. Other types of goal modification/settinginterfaces, interactive elements, goal representations and the like maybe used.

FIG. 90B illustrates another example of a goal setting menu that may beinvoked when viewing a goal tracking interface.

FIG. 90C illustrates another example goal modification interface thatmay include an update goal option button.

In some instances, the user may be restricted to a certain range ofpotential goals. For example, the goal setting/modification functionmight only allow a user to set a goal equal to or above a minimumthreshold and below or equal to a maximum threshold. The thresholds maybe defined as a percentage of a current goal, a percentage of a baselineactivity level (e.g., as determined during an evaluation period), anabsolute amount, a percentage of a maximum activity level (e.g., amaximum amount of activity points ever earned or recorded) and the like.

FIG. 91 illustrates an example notification that may be displayed to theuser upon the user attempting to set a goal below the minimum threshold.

FIG. 92 illustrates an example notification that may be displayed to theuser in response to the user attempting to set a goal above a maximumthreshold. In some instances, the notifications of FIGS. 91 and 92 maybe displayed upon the goal being set to the minimum or maximumthreshold, respectively.

Goals may further be modified even after the user has completed acurrently set goal. The goal increase may be manually triggered (e.g.,by user selection) or may be automatically suggested or recommended tothe user by the mobile application upon the user reaching the currentlyset goal. Allowing the user to increase a current goal (even uponcompletion) may allow the user to further challenge himself or herself,rather than permitting the user to register little to no activity aftercompleting a goal. In one example, modifying the currently completedgoal may be limited to increases to the goal and may be restricted to acertain percentage (e.g., of the current goal or a baseline activitylevel) or an absolute amount. In other arrangements, goalsetting/modification may be unrestricted.

FIG. 93 illustrates an example prompt or notification that may beprovided to invite the user to further challenge themselves byincreasing his or her completed goal. The prompt shown in FIG. 93 mayalso be provided to confirm the user's increase in the completed goalafter the user has selected a desired revised goal.

FIGS. 94A and 94B illustrate additional examples interfaces andfunctions through which a user may modify goals. In some instances, goalmodification options may be generated and provided to the user in themobile application upon reviewing a user's performance over a period oftime. For example, in FIG. 94A, an average of the user's last 3 days ofactivity may be compared to an average goal set for those 3 days. If theuser's average actual activity over that time period was above theaverage goal set or above the average goal by a specified amount, theapplication may suggest or provide an option 9401 for raising the user'sdaily goal. Option 9401 might only be provided under certain conditions.For example, option 9401 may be triggered for the user upon determiningthat the user met the goal for each of the last X goal time periods,that the user exceeded the average goal set by a specified amount (e.g.,10%, 20%, 25%, 50%, etc.), that the user met at least one of the goalsover the last X goal time periods, that the average amount by which theuser exceeded each of the goals met or exceeded a specified thresholdand the like and/or combinations thereof.

On the other hand, if the user may be prompted or provided with anoption 9411 to lower his or her goals, as shown in FIG. 94B, if theuser's average activity level of the past X goal time periods was belowthe average goal level or was below the average goal level by aspecified amount. As with option 9401 (FIG. 94A), various rules(including ones similar to those described above) may be defined fordetermining when option 9411 is to be generated by the application andoffered to the user.

FIGS. 94C and 94D illustrate other example interfaces for modifying orsetting a daily goal while viewing a user's average performance versus aset goal.

A user may further review his or her performance during a goal timeperiod in a variety of ways and the information collected during thegoal time period may be conveyed to provide additional context. FIGS.95A-95C, 96A-96C and 97A-97C illustrate various animations fordisplaying an amount of activity accumulated over a goal time period.For example, in FIGS. 95A-95C, the modification in appearance of a goalobject may be animated in nature to increase the user's anticipation asto the final activity total and to provide the user with an increasedsense of accomplishment. The animation or activity summary for the goaltime period may be conveyed to the user at various times including uponcompletion of the goal time period, during synchronization of activitydata from an activity tracking device, upon the user selecting an optionto review his or her activity level for a particular goal time period,in response to the user completing a goal (e.g., the animation or reviewmight not be displayed if the user does not complete the goal for thegoal time period), in response to the user reaching a milestone orachievement other than the goal itself

FIG. 95C illustrates an interface in which the activity review for thegoal time period (or an animation thereof) is complete. The interfacemay display a message indicating whether the goal was met, not met,exceeded, and/or an amount by which the goal was exceeded. The interfacemay also include an option to share the activity recorded for that timeperiod, as will be described in additional detail herein.

FIGS. 96A-96C and 97A-97C illustrate other example animations andactivity review interfaces that may be displayed in various situations.For instance, the animation of the progress bar and/or the appearance ofthe progress bar may differ if the user exceeded the goal by variousamounts, if the user did not meet the goal and/or if the user met thegoal, but did not exceed the goal by specified amounts. In FIGS.96A-96C, for example, the progress bar 9601 may be displayed with an icyappearance to represent that the user exceeded the goal for the timeperiod by 20%. Other attributes of the animation may also differincluding a rate at which the progress bar 9601 grows, backgroundcolors, patterns, animations or schemes, additional animations ancillaryto the growing of the progress bar 9601 (e.g., ice chips or piecesfalling away from the progress bar 9601) and the like.

In FIGS. 97A-97C, the progress bar 9701 may be displayed with a fieryappearance upon determining that the goal for that time period wasexceeded by 50%.

While the activity tracking application is configured to trackindividual goal time periods and completion (or non-completion) of goalsfor those individual time periods, the activity tracking application mayfurther provide feedback and review information relating to multiplegoal time periods. In one example, the activity tracking application maytrack and monitor activity streaks. Streaks may include the completionof multiple goals corresponding to multiple consecutive goal timeperiods. Streaks might only be recognized when the user has completedgoals for X number of consecutive goal time periods, where X may be anynumber greater than 1 (e.g., greater than or equal to 2). The trackingand recognition of streaks may provide a further motivating factor forthe user to maintaining and/or elevating his or her activity level andto meet all goals. Streaks also encourage consistency which may lead tothe adoption of a healthier or more active lifestyle. The user may beawarded with rewards or types of recognition including coupons, freeproducts, virtual items including virtual apparel, icons, images etc.,services, event tickets and the like. In some examples, a reward mayinclude unlocking a new color or image to be used on a activity trackingdevice or in the mobile application. Additionally or alternatively, whena user has achieved a streak, an indication of the streak and/or rewardmay be transmitted to a wearable device through which activity is beingtracked.

FIG. 98A illustrates an example activity tracking interface portion inwhich a goal completion status for each of a number of goal time periods9801 is displayed. The completion status may be represented by anindicator or icon such as icons 9803 and 9805. Icon 9803 may indicatethat the goal was met for that goal time period while icon 9805 mayindicate that the goal was not met. Streaks indication portion 9807 mayfurther convey to the user whether the user is on a streak, starting astreak, just ended a streak or the like. In some examples, portion 9807may provide motivating messages to begin or continue a streak. Goal timeperiods that have yet to occur may be displayed in yet another visualmanner. In one example, a current goal time period may be displayeddifferently from completed goal time periods and goal time periods thathave yet to occur. In one example, the beginning of a streak maycorrespond to an instance where a user's currently completed activitygoal is the second of two consecutive goal completion time periods andthe number of consecutive goal completion time periods of which thecurrently completed activity goal is a part) is equal to 2. Breaking astreak, on the other hand, may correspond to a first goal time period inwhich the user did not complete a goal occurring consecutively after atleast two consecutive goal time periods where the activity goal wascompleted.

When the user achieves a particular streak (e.g., of 3 days) for thefirst time, the application may provide a celebration or recognition asshown in FIG. 98B. The celebration of this milestone or achievement mayfurther motivate the user to continue the streak to achieve even greaterrecognition for longer streaks. The streak achievement may be providedas a reward or a trophy and the recognition may further be shared in avariety of ways including through e-mail, social networking messaging,text message and the like and/or combinations thereof. FIG. 98Cillustrates streak indication portion 9807 upon the user completing thegoal for the current goal time period and achieving the 3 day streak.Sharing and tagging options may also be provided in the activitytracking interface, as is described in further detail herein.

FIG. 99 illustrates another example streak achievement for which a usermay be recognized. In particular, beating the user's existing best(e.g., longest) streak may be provided as an achievement, and the newbest (e.g., longest) streak may be recognized. A streak may be evaluatedfor being the best streak each time the streak is extended or upon theuser breaking the streak. Various other streak evaluation rules may bedefined as desired by an activity monitoring service, the user and/orother entities.

As noted above, a user may tag his or her activity with variousinformation. Tagging may provide a way in which a user associatesvarious emotions, location information, equipment information, weatherinformation, terrain information, activity partner information and thelike with a particular activity time period. The tagging information maybe specified by the user, automatically detected by the mobile device,automatically detected by the wearable activity tracking device and/orretrieved from other devices. In one example, the wearable device and/orthe mobile device may include a location determination component such asa GPS device or cellular triangulation modules. In such an example, thewearable device and/or the mobile device may automatically populatelocation information if the user wishes to tag recorded activity. Inanother example, weather information for a location may be automaticallyretrieved from a weather database.

FIG. 100A illustrates an interface through which a user may tag anactivity session with the user's mood, attitude or subjective perceptionof the activity session and/or type of activity performed. The mood orattitude may be specific to the activity performed during the activitysession or may relate to the time period in general.

FIGS. 100B and 100C illustrate various emotion, mood or attitudeselection menus in which various icons or images 10001 may representdifferent emotions, moods or attitudes. In some examples, selecting oneof the icons or images 10001 may cause pre-defined text to be enteredinto text entry field 10003. The user may be allowed to edit the text inentry field 10003 or the text may be non-editable. In other examples,the selection of one of the icons or images 10001 might not includeautomatic population of pre-defined text. Instead, text entry field10003 may remain blank and editable. Text entry field 10003 may enablethe user to record additional thoughts or feelings regarding theactivity time period and/or the activity performed during the timeperiod. Once the user elects to save the information (e.g., selectedrepresentative image, entered text, etc.), the tag information may bestored in association with the activity time period and activity datarecorded for the time period. In association with or separately from thesubjective feeling tag such as mood, emotion or attitude, the user maytag the activity with a photograph. The photograph may convey additionalsubjective or objective information about the activity including alocation, weather, the user's mood at that particular day or time andthe like. Tags may be specific to an overall goal time period, aspecific time, a particular activity session, a particular range oftimes and the like.

In addition to tagging, the user may share activity information withothers through various channels. In one example, the activityinformation may be posted to a user's profile or account on an activitytracking service site. In other examples, the activity information maybe posted through an internal or external social networking system. FIG.101 illustrates an example sharing menu 10101 providing multiplechannels through which activity information may be shared with otherusers.

In one example, posting to a FACEBOOK account may include theapplication automatically generating a template or standard post, asshown in FIG. 102A. The post may include predefined language and images10201 along with user-specific activity data including goal information,whether the user completed the goal and/or a level a completion (e.g.,exceeded the goal by 50%). The post may further include identificationof equipment used to track the activity. This may help encourage otherusers to increase their activity level and identify help products andservices for doing so. The user may further enter comments or otherinformation in field 10203 and submit the post via option 10205.

FIG. 102B illustrates an example post that may appear on the user'sFACEBOOK page upon submitting the post shown in FIG. 102A to FACEBOOK.In some arrangements, the message posted to the user's FACEBOOK accountmay include a link to the user's profile on an activity tracking servicesite and/or to activity tracking product and service information pages.

FIGS. 103A and 103B illustrate an example TWITTER posting interface andresulting TWITTER post, respectively.

Visual appearance of a user's activity level may help convey varioustypes of information and messages about the activity level to the user.As described herein, different colors may be used to represent differentlevels of goal completion or non-completion. FIGS. 104A-104C illustrateexample interfaces displaying activity level graphs for a goal timeperiod. In addition to the graph of activity level over time, theinterface may further include summary portion 10401 in which the amountof activity point earned is displayed as well as an indicator 10403showing whether the user completed the goal. The color of indicator10403 may convey an additional detail. In particular, the color ofindicator 10403 may represent an amount by which the goal was missed.For example, indicator 10403 appearing in red may indicate that the useronly achieved 25% or less of the goal while if the indicator 10403appears in yellow, the user may recognize that they achieved over 25% ofthe goal but less than 100%. The appearance of line 10405 in graph 10407may adopt similar color schemes and visual indications. Other visualcharacteristics, animations, audio indicators may also be used to conveyadditional activity data including patterns, transparency levels,highlighting, brightness, size of indicators or graph elements, speed ofanimation, type of animation, audio messages and the like.

FIGS. 104D-104F illustrate other example interfaces displaying acivitylevel graphs for a goal time period such as a day. In addition oralternatively to the information shown in FIGS. 104A-104C, theinterfaces of FIGS. 104D-104F may include a mood indicator representingthe user's current subjective feeling about the goal time period, anactivity, an activity session and the like. The user may be able tomodify the mood indicator throughout the goal time period and duringactivity sessions performed therein. Alternatively or additionally, themood indicator may be automatically set by the application based on alevel of activity performed and predefined rules correlating the levelof activity to a mood and mood indicator. For example, if the user hasexhibited a high level of activity (above a first threshold), the moodmay be set as happy or excited. In another example, if the user exhibitsa low level of activity (e.g., below a second threshold), the mood maybe set as sad or disappointed or the like. One or more other thresholdsmay be set as desired by the user or as defined by the system or anactivity tracking service.

FIG. 105 illustrates an example activity summary for multiple activitytime periods. In addition to the bars representing each activity timeperiod, the summary 10500 may further include an indicator 10501identifying the goal. Indicator 10501 may be used to convey an amount bywhich a goal was exceeded or an amount by which a user underachieved.

FIGS. 105A-105D illustrate other example activity summaries for multipleactivity periods. For example, FIGS. 105A and 105B illustrate examplemonthly summaries for daily goal periods. The summary may include acounter indicating a number of goal periods in which the goal wasreached and a number of total goal periods during the month. A totalamount of activity points for the month may also be displayed. As notedabove, each goal period may be represented by a bar or other type ofgraph to indicate a performance during that period. Different colors orother types of visual characteristics may be used to represent whether auser completed the goal and if not, a level of progress made toward thegoal. For example, green may represent goal completion, while yellowrepresents completion up to a certain threshold (e.g., 50%-99%) and redrepresents completion below a specified threshold (e.g., below 50%).Degree of completion may be conveyed in various other manners as well.

FIGS. 105C and 105D illustrate an example activity summary for a year.Similar statistics and information may be provided in a yearly summaryas was discussed with respect to the daily and monthly summary views.Summaries based on a time period may correspond to a rolling time periodand thus, may show data from a past month, past week or past year endingwith a current time. In the examples illustrated, the summaries of thetime periods begin and end at calendar weeks, months and years. As such,some of the data may be empty if certain dates and times are in thefuture.

FIGS. 106A and 106B illustrate example interfaces in which tags and, inparticular, subjective perception tags may be displayed for multipleactivity time periods. These subjective perceptions (e.g., moods,attitudes, other subjective feelings) may further be shared.

FIGS. 107A and 107B illustrate example interfaces through which activityinformation and events may be conveyed and viewed. For example, FIGS.107A and 107B illustrate portions of an activity feed that displaysactivity levels and other data such as achievements (e.g., whether thegoal was completed or missed, streaks, milestones, records, etc.), tagsand the like in a list format organized according to activity timeperiod (e.g., day). The activity feed may provide a way for a user todigest activity information for multiple activity time periods through asingle interface or display. In some arrangements, the user mayconfigure the types of information that are included in the activityfeed based on their specific interests.

FIGS. 107C-107E illustrate other example interfaces through whichactivity information and events may be conveyed. In FIGS. 107C-107E, auser's tagged mood or subjective feeling about the goal time period oractivity session may also be indicated in the feed/listing. Selectingone of the entries in the feed may provide the user with furtherinformation about the goal time period or activity session.

FIGS. 108A and 108B illustrate example user profile or accountinterfaces through which the user's activity information may beconveyed. In one or more arrangements, the user profile may include amilestone or achievement tracker 10801 (as shown in FIG. 108A). Themilestone tracker 10801 may be used to track a goal or achievement thatspans multiple time periods or is unrestricted in time (e.g., nospecified end date for the goal). For example, users may receivemilestone awards or recognition upon reaching various lifetime activitypoint totals. Accordingly, tracker 10801 may be used to identify auser's progress toward such achievements or milestones. In someexamples, the milestone or achievement tracker 10801 may also bedisplayed in other interfaces including a home interface in which adaily activity level and goal are tracked, an activity review interfacein which activity recorded for a single or multiple time periods may bereviewed and the like.

FIG. 108B illustrates another portion of the user profile interface inwhich records and trophies may be displayed. Trophies may includeimages, icons, virtual items and the like representing a particularachievement or milestone. In some examples, the trophies may also bedisplayed with a number of times won or achieved to provide incentivefor users to reach the same milestone multiple times.

The mobile application may be configured to track still additional typesof activity data including a best activity time period for a category oftime periods. In the example illustrated in FIGS. 109A and 109B, eachactivity time period may correspond to a single day. Accordingly,activity time periods may be grouped into days of the week and analyzedto determine a best activity time period for each of the days of theweek. This information may then be conveyed to the user and may aid indetermining days for which activity needs to be improved. Categorizationor grouping of activity time periods may also correspond to months,years, times of day (e.g., afternoon, evening, morning), user-definedgroups (e.g., the user may manually assign activity time periods todifferent predefined or user created groups), type of device used todetect or record the activity, location of activity, type of activity,instructor (e.g., for athletic activity classes), activity partners,times of year (fall, spring, winter, summer) and the like. The bestactivity time period may be defined in multiple ways including highestactivity point total, most activity points accumulated within aparticular sub-time period (e.g., between the hours of 8 AM and 8 PM),greatest improvement over a previous activity time period (e.g., animmediately preceding time period), largest amount by which the activityrecorded exceeded a goal (e.g., when the goal differs from time periodto time period).

Additionally or alternatively, other category-specific statistics may begenerated for each of the groups or categories including activityaverages, highest and lowest activity levels, most active subtime-periods for the category and the like. Sub-groups or categories mayalso be defined within each category or group. For example, activitytime periods may initially be grouped by day of week. Each day of weekcategory may further be categorized by time of day or time of yearand/or the like. Accordingly, not only might category-specificstatistics and information be determined, sub-category-specificstatistics and data may also be generated. Further levels ofsub-categories may be defined or used as desired.

Moreover, various triggering events may cause the mobile application togenerate notification messages to the user. The messages may beimmediately displayed to the user without user request or prompting ormay be stored for user retrieval. For example, in FIGS. 110A and 110B,the home interface 11001 and the profile interface 11003 may bothdisplay indicators 11005 that identify available notifications and anumber of notifications. The indicators 11005 may be overlaid onelements of the interfaces 11001 and 11003 with which the user mustinteract in order to view or otherwise retrieve the notificationmessages.

FIG. 111 illustrate examples notification messages that may be providedto the user.

FIGS. 112A-112C, 113A-113C, 114A, 114B, 115A and 115B illustrate otherexample interfaces that may be generated and displayed for conveyingvarious milestones, achievements and/or other accolades. For example,FIGS. 112A-112C illustrate interfaces for reaching a best day mark whileFIGS. 113A-113C illustrate interfaces for exceeding a best day of week.FIGS. 114A and 114B illustrate example interfaces for reaching alifetime activity point mark (e.g., 25000). FIGS. 115 and 116 illustrateexample interfaces indicating that the user has earned activity pointsfor a particular number of days or time periods. These achievements,awards and accolades may be shared as described herein.

The activity tracking application may include various settings forcustomizing the applications functions. FIG. 117 illustrates an examplesettings menu 11701 that may be used to modify a user's profile, dailygoal, display features, communication preferences and sharing options.In one example, a user may login to or otherwise specify authorizationinformation for one or more sharing sites or services such as FACEBOOKand TWITTER. The application may then use the authorization informationor login to interact with the user's account on those services.

FIGS. 118A-118C illustrate example profile setting interfaces. Inaddition to the desired units of measure and the user's height, weightand gender, profile setting interface 11801 (FIG. 118A) may furtherinclude a profile picture option 11803 and an option 11805 tosynchronize data from a wearable activity tracking device. Selecting theprofile picture option 11803 may provide multiple picture settingoptions such as those shown in FIG. 118B. For example, the user mayselect a picture or image from a library to take a picture using acamera of the mobile device. In some examples, profile pictures orimages may also be retrieved from a remote site through a network suchas the Internet. In a particular example, the user may retrieve imagesfrom his or her social networking account. In still another example, aprofile image on a user's social networking account may be automaticallypopulated as the user's profile image in the activity trackingapplication and/or the user's account on a corresponding activitytracking service and site. Upon selecting or capturing an image for theuser's profile, the user may be provided with an image editing interfaceas shown in FIG. 118C. The user may have the option to crop, resize,rotate, scale and perform other image editing on the image beforesetting the image as his or her profile picture. Additionally oralternatively, the profile settings entered through the application maybe synchronized and uploaded a user's account with a correspondingactivity tracking service and site. Accordingly, any changes made theuser's profile on the mobile application may be reflected automatically(or in an on-demand fashion) to a user's account on a remote networksite.

FIGS. 142 and 143 illustrate other example setting interfaces. Forexample, FIG. 142 illustrates an example settings menu in which variousoptions are provided to the user including account settings, devicesettings specific to a user's monitoring device and social networksettings. The monitoring device-specific settings may include a dailygoal setting, device display settings, help and support information.Different devices may include different types of settings and thus thedevice-specific settings portion of the menu may differ from device todevice (e.g., depending on what devices are connected). Daily goalsettings may be defined as described herein. For example, users maymanually enter a goal value or specify that they wish to increase ordecrease a previous goal by a certain amount. In another example, a usermay specify that they wish to set their goal based on an amount ofactivity points accumulated in a previous goal period. The user mayindicate, for instance, that they wish to exceed the number of activitypoints accumulated in a previous goal period by 10%, 15%, 20%, 50%, 100%and the like. The goal may also be set to be lower than the number ofpoints accumulated in the previous goal period.

FIG. 144 illustrates an example device display settings interface.Through this interface, a user may control various parameters of adevice's display or displays. For instance, the user may indicate whatmetrics are to be displayed including steps, calories and the like. Uponturning off one or more of these metrics, the metrics may be removedfrom an information display loop of the monitoring device such that theuser may no longer view the metric through the device. The user mayfurther indicate a wrist or hand on which the device is worn to helpconfigure an orientation of text or other information that is displayedon the display(s) of the device. Other wear locations may also beprovided in the list of options. For example, users may wear devicesaround their neck, on a belt around their waist, on a shoe, in a shoe,around their head, around the user's knee or elbow, ankle and the like.Depending on the wear locations various display and devicecharacteristics may be set. For example, if the user is wearing thedevice at a location that is not easily visible while performingactivity, the device may be automatically configured to use hapticoutput or audio output and/or to deactivate one or more displays. Inanother example, if the user is wearing the device in a visiblelocation, one or more displays may be activated. In still otherexamples, haptic or audio output may be configured in terms of level ofsensation or force and/or volume based on the location at which thedevice is worn. For example, the farther away from the user's ear thedevice is worn, the louder the volume may be set. Haptic feedback levelsmay be set at a higher level (e.g., amount of force) when the device isworn in a less sensitive area and set to a lower level when worn in amore sensitive area. These configurations may be automaticallydetermined and set by the device and/or configuration system based onpredefined rules. In some examples, the user may configure multipledisplays of a device if the device includes multiple displays. Forexample, different setting options and values may be defined for each ofdisplays 18 and 20 of device 10. Other settings of the display may becontrolled including colors used, font sizes, font styles, types ofanimations, language, images and the like. Additionally oralternatively, the algorithms for identifying and/or measuring activitymay also be automatically selected by the device and/or configurationcomputing system based on the wear location or other configurationoptions.

In some arrangements, activity may be detected and activity points maybe accumulated regardless of a type of activity that was performed. Inother arrangements, activity may be tracked along with the type ofactivity that was performed. FIGS. 119A and 119B illustrate exampleactivity tracking interfaces that are configured to track a total amountof activity performed by the user as well as a type of activity. Forexample, option 11901 may be used to select a type of activity.Additionally or alternatively, option 11901 may be used to groupactivity detected into discrete sessions. The sessions may be smallerthan, greater than or equal to a goal time period or other generalpredefined activity period. For example, the user may tag a portion ofactivity performed during the day as “Gym time” or “After work.” Inanother example, a user may specify that a week of activity correspondsto a vacation time period. Other activity or time period designationsmay be used as desired or needed.

FIGS. 120A-120C illustrate example location marking interfaces that maybe used by a user to identify a workout location upon completion of theactivity session. For example, in FIG. 120B, a location may beautomatically defined by the system based on the detected coordinateinformation and a database of buildings or places corresponding to thosecoordinates. A user may be able to edit the specified location, forexample as shown in FIG. 120C, by selecting a different suggested ormatched building or place. A building or place may be identified by aname, street name, address or other designation other than latitudinaland longitudinal coordinates.

FIGS. 121A-121C illustrate the ability for a performance trackingapplication to record a route taken by a user. The route may bedisplayed on a map and various indicators may be displayed on the route.For example, indicators 12101 as shown in FIG. 121C may indicateparticular known places that are near or along the user's route. Colorof the route may also specify a number of calories burned, speed, pace,user's mood, terrain type (e.g., cobblestone, gravel, asphalt, incline,decline, flat, etc.) and/or combinations thereof. Hovering over any ofthe indicators or portions of the route may provide further informationsuch as a name of a place, an amount of athletic activity performed atthat point, terrain type, user's mood, speed and the like.

Upon completion of, during or prior to an athletic workout, a user maydesignate a type of activity that was performed, is being performed orwill be performed. This may allow the application to better calibratesensor data and algorithms to measure performance. For example,accelerometer signals may appear differently depending on the type ofactivity (e.g., cycling versus squash). Accordingly, different dataprocessing algorithms may be used to more closely align the data withthe user's actual amount of activity (e.g., steps taken, caloriesburned, miles run or moved).

FIGS. 122A-122C illustrate example user interfaces through which a usermay select the activity type. Upon selection of the activity type, theapplication may automatically identify and use a corresponding algorithmto process sensor data. The identified activity type may further bestored in association with the activity data collected during theperformance of the activity. The beginning and end of the activityperformance may be marked or identified by the user or may beautomatically marked or identified based on detecting periods ofinactivity reaching a specified threshold.

Additionally or alternatively, the activity monitoring application mayautomatically suggest a location and/or activity type. FIGS. 123A and123B illustrate an application interface through which a suggestedlocation and activity type are determined. The location may bedetermined based on a database of previous activity locations or workoutlocations used by other users or a general database of locations andplaces defined by coordinates. The activity type, on the other hand, maybe determined based on matching the sensor signal with signals of knownactivities. If there is a substantial similarity between the signal inquestion and a signal for a predefined activity, the application maysuggest or define the user's activity as the predefined activity. Inother examples, activity type may be automatically suggested ordetermined by associating an activity type with a location. The locationmay have been previously stored by the user and a type of activity mayhave been previously associated with the location (e.g., by the user).For example, the user may have identified that he or she was running ata high school. Accordingly, the application may automatically suggest arunning activity type if the user's location is determined to be thehigh school. In other examples, the application may identify a type ofbusiness or location through on-line directories or network databasessuch as on-line business listings and the like. The application may theninfer, based on the type of business or location, a type of activitythat the user is performing. For example, if the user is located at anaddress corresponding to a yoga studio, the application may suggest thatthe activity type corresponds to yoga. Other methods and techniques fordetermining an activity type may also be used.

FIG. 124A-124C illustrate example activity tracking interfaces in whichan activity type is identified. In FIG. 124A, for example, the type ofactivity contributing to the activity total is indicated in portion12401 using images or icons 12403. Icon 12403 may represent the type ofactivity such as running, aerobics, biking, weight lifting and the like.FIG. 124B illustrates an interface with multiple activity typesindicated.

FIG. 124C illustrates an example breakdown view in which thedetected/recorded activity is divided into contributing activity type.For example, each of a biking, walking and running activity type isdisplayed along with a corresponding amount of activity of that activitytype performed. Graph 12411 may display an amount of activity by typeversus time. The amount of activity corresponding to each of theactivity types may be distinguished in various manners including usingdifferent colors, patterns, shapes, sizes, transparencies, color orgrayscale gradients and the like and/or combinations thereof.

FIGS. 125A-125C, 126A-126C, 127A-127C, 128A-128C, 129A-129C, 130A-130C,131A-131C, 132A-132C, 133A-133C and 134A-134C illustrate additionalexamples of activity tracking interfaces in which activity type may beused to categorize or divide the performed activity. In FIG. 126C, forexample, each arcuate portion 12601 a, 12601 b and 12601 c maycorrespond to a different activity. The portion filled in in each ofarcuate portions 12601 a, 12601 b and 12601 c may correspond to a timeof day at which the activity was performed.

In another examples, FIG. 134C may illustrate a user's activity in theform of interlocking shapes or blocks 13401. The different shapes of theblocks or color of the blocks may correspond to the activity type.Additionally or alternatively, the size of the shapes may correspond tothe amount of activity of that type that was performed. Other variationsof visual or graphical representations may be used to represent activitytype, amount of activity of that activity type and/or a time at whichthe activity of the activity type was performed in the same image orusing different images. Activity may be summarized according toalternate or additional categorizations and divisions as desired andsuch categorizations may also be reflected and conveyed visually.

FIGS. 135A-135D illustrate a series of interfaces through which a usermay tag activity session with friend information. For example, a usermay add friends to a activity session by searching through a list offriends or by defining a new friend. This information may then be storedin association with that particular session. More than one friend may beadded to the activity session, if appropriate or desired.

FIGS. 136A-136C illustrate example interfaces for displaying aggregateactivity information for activities performed with friends. Friends maybe organized according to an amount of activity performed with thatfriend overall (FIG. 136A) or for a specific type of activity (FIG.136B). Selecting a friend, as shown in FIG. 136C, may display the user'sprofile as well as common activity interests and/or shared activitylocations.

FIGS. 137A and 137B illustrate example competition or game interfacesthat may be displayed when a user chooses to compete with a friend. Theinterfaces may also be used to provide a comparison between the amountof athletic activity performed by the user and another user.Accordingly, a user may select any friend or user with which to compareathletic activity, as shown in FIG. 137B. A graph may then be displayed,as shown in FIG. 137A, illustrating a comparison of athletic activity. Avariety of graphs and comparison formats may be used.

FIGS. 138A and 138B illustrate a series of interfaces through which auser may access a leaderboard identifying where the user places amongall friends or users or a group. The user may be highlighted by anindicator such as a rectangular outline or highlighting.

FIGS. 139A and 139B illustrate example achievement interfaces configuredto provide a user with encouragement or an indication of someachievement such as a new personal best (e.g., for a 1 mile run) orcompletion of a goal (e.g., running 10 miles for the first time).

FIGS. 140A and 140B illustrate example interfaces that provide specialaccess to events or locations. The interfaces may include a scanningcode or pattern 14001 that may be scanned (on screen) by event or placestaff to verify authenticity and admittance. Such interfaces may alsoinclude discounts or other special offers for products, services, fooditems and the like.

According to another aspect, joint or multi-user goals may be defined toprovide team-oriented activities. In one example, an overall goal may bedefined for a group of users, where each user is required to complete aportion of the overall goal. Activity in excess of one user's portionmight not be applied to the overall goal or contribute to completion ofanother user's portion of the goal so that each user must complete hisor her own portion. This may encourage the users to perform the activityrequired due to peer-pressure or a sense of responsibility if theoverall goal is not reached. In other arrangements, excess activity byone user may contribute to the completion of another user's portion ofthe goal. Limits may be set to an amount of activity that may becontributed to other user's goal portions. In yet other examples, themulti-user goal might not have predefined user portions. Accordingly,users may contribute as much as they would like to the overall goal.

Multi-user goals may include visualizations or user interface elementsthat celebrate the goal achievement upon completion. For example, theoverall goal may be represented by a set of bowling pins. Each user maybe responsible for knocking his or her pin down by completion his or herportion of the overall goal. Upon a user completing his or her portionof the goal, an appearance of a corresponding bowling pin may change toappear knocked over. Once all users have completed their goal portions,a celebratory message, visualization or other indicator may bedisplayed.

FIG. 141 illustrates another example visualization for a multi-usergoal. In this example, two users may be jointly attempting to achieve agoal of accumulating 6,000 activity points. The first user's progress14101 may be represented by a bowling ball while the second user'sprogress 14103 may be represented by a set of bowling pins. In order tovirtually knock down the bowling pin, the users may be required to movetheir progress bars to a middle portion where the bowling ball and thebowling pins would meet. Accordingly, the users may be required tocomplete their own portions in order to achieve the goal. The goalportions, as illustrated, are evenly divided. However, the goal portionsmight not be evenly divided and one user may be required to perform moreactivity than the other. Various goal splits may be used and/or definedas selected by a user, a coach, an activity tracking service or thelike.

As described, the device 10 or device 4300 (FIG. 43) is capable ofinteracting with another device 10. Accordingly, a first user wearingthe device 10 can compare their activity with the activity of a seconduser wearing a second device 10. The indicator system 20 on the devicecan indicate a first level of activity of the first user while alsoindicating a second level of activity of the second user. Similarly, theindicator system 20 on the second device can indicate the second levelof activity of the second user while also indicating the first level ofactivity of the first user. The activity data of the other user can becommunicated to the other device via wireless communication from amobile device or remote site. In this configuration, the plurality oflights of the respective indicator system can be considered to bedivided into a first segment and a second segment. The first segment maycomprise a first group of ten of the light members while the secondsegment may comprise a second group of ten of the light members. Thus,the first user's activity level is displayed on the first segment of theindicator system and the second user's activity level is displayed onthe second segment of the indicator system. The indicator system may beilluminated when a user depresses the input button to check progress ofeach user's activity level. In this aspect of competition between twousers, there is no end goal. If one of the users reaches the full meterlimit on the indicator system, the system will increase the upper limitand adjust each of the user's progress levels.

In another aspect, a first user and a second user can compete in a “tugof war” competition. Each user's respective indicator system displaysboth user's activity levels. For example, the first user's activitylevel is displayed in a first color and the second user's activity levelis displayed in a second color. In comparing respective activity levels,each user tries to take over the other user's indicator system byincreasing their respective activity levels where more light members ofthe indicator system is illuminated with their respective color.

In another aspect, the device 10 may be programmed to display activitylevels in a particular color for a set period of time. For example, auser may be performing activities and earning activity points for acharity. In such case, the indicator system may illuminate all of thelight members in a designated color such as white. Also, if the user wasparticipating in a particularly sponsored event, activity relating tothat event could be displayed in another designated color.

In another aspect, one can provide motivational messages to a user suchthat the message is conveyed via the display or indicator system. Forexample, a motivational message may be loaded onto a remote site by afirst user and directed to a second user. The message may be loaded ontothe second user's device such as when the second user plugs the deviceinto the computer. The message may be downloaded to the second user'sdevice 10 stored therein. The second user may not immediately be aware amessage has been received. The motivational message could be triggeredby an event such when the second user reached a goal. Upon a triggeringevent, the indicator system of the second user's device may beilluminated in a certain fashion such as all light members blinking.Audible sounds could also be provided or other animated lightingfeatures on the display or indicator system. It is further understoodthat the triggering event could be based on other parameters such astime, or the motivational message may be provided immediately upontransferring to the device. Finally, it is understood that themotivational message may be delivered wirelessly to the device 10. It isfurther understood that a message could be delivered to the device forthe user to check an associated mobile device for the message.

In another aspect, an alert message can be delivered to the device 10wherein the indicator system may be illuminated in a certain designatedmanner. The alert message may be delivered and triggered in any of themanners as described herein. The alert message may indicate that theuser should visit a remote site for further information or to look for amessage on the user's mobile device. In one exemplary embodiment, thealert message could indicate that a reward is possible for activityperformed at a particular time.

In another aspect, the device 10 may provide a message based oninactivity or non-active periods. If the device 10 senses that the userhas been in a non-active (e.g., low activity) state for a predeterminedamount of time, an alert message may be delivered to the indicatorsystem or display to remind the user to become more active. The alertmessage can be delivered in any of the manners described herein. Thethreshold levels of a low activity state and amount of inactive timecould also vary and be individually set by the user.

In some arrangements, user non-activity or inactivity may also bedetected and affect the user's progress toward completion of an activitygoal. For example, inactivity may be detected when a user does notexhibit movement of a particular level or a type of movement for aspecified amount of time, does not exhibit a heart rate of at least athreshold level, does not move a sufficient amount of distance over anamount of time and the like and/or combinations thereof. Forarrangements in which a user accumulates activity points to reach anactivity point goal, points or a value may be deducted from the user'sactivity point or other activity metric total when an amount ofnon-activity (e.g., inactivity or sedentary state) is detected. Variousconversion rates for converting inactivity to activity point deductionsmay be used. In a particular example, 10 minutes of inactivity maycorrespond to a 5 point deduction. In another example, 30 minutes ofinactivity may correspond to a 100 point deduction. Loss or deduction ofactivity points may be linear or may be non-linear, for example,exponential, parabolic and the like.

As noted herein, current progress may be indicated by an indicatorsystem such as system 20. Current progress indication may be triggerednot only based on an increase in goal progress, but also a decrease ingoal progress. For example, if activity points or a threshold amount ofactivity points are deducted from the user due to inactivity, a currentprogress indication may be displayed. For example, a lighting element ofsystem 20 corresponding to a user's current level of progress may beilluminated. Alternatively or additionally, an alert may be displayed ina primary display such as display 18 indicating that points werededucted and/or that the user has been inactive for a specified amountof time. In a particular example, progress may be indicated on anindicator system such as indicator system 20 using intervals ofprogress. Each interval may represent an amount of activity points andmay correspond to a different indicator lighting element in indicatorsystem 20. In such an example, the threshold number of activity pointsmay correspond to a difference between a user's current amount ofactivity points and an upper activity point boundary for a lowerinterval of progress. In other examples, any decrease in activity pointsmay cause a current progress indication. Accordingly, the user mayreceive immediate notification that his or her progress has decreased.

A user's non-active time may include inactive time and sedentary time.Inactivity and sedentary time may be defined by different movement,heart-rate, step or other thresholds or may be defined using the samethresholds. In one example, sedentary time may have a higher threshold(e.g., requiring a higher level of activity) than an inactivitythreshold. That is, an individual may be considered sedentary but notinactive. The non-active threshold may correspond to the sedentarythreshold or a higher threshold, if desired. Alternatively, aninactivity threshold may be greater than a sedentary threshold. Theremay also be multiple sedentary thresholds, inactivity thresholds and/ornon-active thresholds (e.g., each of the sedentary and inactivitythresholds may be a non-active threshold). Different point deductions orrates of point deductions may also be defined between the multiplethresholds and levels of little to no activity (e.g., non-activity). Forexample, a user may lose 50 points per hour for inactivity and 30 pointsper hour for sedentary activity or vice versa. Further, activity pointdeduction may be triggered at different times depending on if the useris inactive or sedentary. For instance, a user may begin losing activitypoints after 30 minutes of inactivity or 45 minutes of being sedentary.Additional thresholds (e.g., more than two thresholds) and correspondingrates of activity point loss may also be defined.

In some arrangements, various sensors may be used to detect non-activeperiods of time. As discussed, non-activity time periods may be definedbased on heart-rate, amplitude of a movement signal, step rate (e.g.,<10 steps per minute), or the like. Alternatively or additionally,inactivity and sedentary time periods may be measured based on aphysical position, body position, body orientation, body posture of ortype of activity being performed by the individual. The detrimentaleffects of various physical inactivity or sedentary body positions ororientations may also differ. Accordingly, 30 minutes of reclining mayintroduce the same health risks as 45 minutes of sitting. The potentialfor health risks may also be time-dependent. Accordingly, non-activity(e.g., sleeping) for a specified range of durations and during aspecified range of time might not introduce health risks. In oneexample, sleeping for 7-9 hours between 9 PM and 9 AM might notintroduce detrimental health risks and thus, might not contribute toactivity point or other activity metric value deduction. Indeed, in someexample, a lack of inactivity (such as sleep) for a specified range ofdurations and/or during a specified range of time may be considereddetrimental to a user's health. Thus, activity points may be deducted oractivity points may be accumulated at a slower rate during these times.

Alternatively or additionally, the amount by which a value of theactivity metric (e.g., an activity points) is decreased may bedetermined based on time of day, location of the user, physical positionof the user, level of inactivity and the like. For example, a user maylose greater value in an activity metric and/or at a faster rate duringthe afternoon than during the evenings. In another example, if a user isat a gym, the user may lose fewer activity points or other activitymetric or lose value in the metric at a slower rate than if the user waslocated at home.

To account for the variances in types of non-active activity (e.g.,below a requisite level of movement to be considered activity), a systemmay distinguish between physical body positions or orientationsincluding, for example, sleeping, reclining, sitting and standing.Distinguishing between different physical body positions andorientations may include placing sensors at different locations of theuser's body to detect the individual positions of each body part. Thephysical body position of the user may then be determined based on therelative positions of the body parts to one another. For example, when aknee location sensor is within a first threshold distance of a waist orchest sensor, the system may determine that the user is sitting. If theknee location sensor is outside of the first threshold distance, thesystem may determine that the user is standing. In the above example,the system may use a portion of the distance such as the verticaldistance. By using vertical distance alone or in combination with anabsolute distance (e.g., straight line distance between the twosensors), the system may further distinguish between when a user islying down and standing up. For example, a lying down position maycorrespond to a very low vertical distance between the knee sensor andchest or waist sensor even though the absolute distance may be larger. Astanding position may correspond to a larger vertical distance betweenthe knee sensor and the waist or chest sensor but exhibit a similarabsolute distance. In other examples, an angle formed by the varioussensors may be used to determine an individual's position. Additionallyor alternatively, the location of the user's various body parts may beevaluated in conjunction with accelerometer or movement data todetermine if the user is exhibiting movement or (e.g., at, above orbelow) a specified level of movement.

In addition to deductions in activity points, the system may alert auser to inactivity to encourage active lifestyles. In one example, thesystem may alert the user by displaying a message or indicator on adevice such as the wearable device assembly described herein after aspecified amount of inactivity such as 2 minutes, 5 minutes, 30 minutes,1 hour and the like. The amount of inactivity time may be additive overnon-consecutive time periods. An amount of consecutive inactivity timemay alternatively or additionally be tracked. For example, if the useris inactive between 10:15 and 11:00 AM and then again between 2:00 and2:30 PM, the total amount of non-active time may be 1 hour and 15minutes. The message or indicator of inactivity may be provided as awarning prior to deducting activity points. For example, the message mayindicate that X amount of activity points will be deducted if the userdoes not exhibit a sufficient level of activity within a specifiedamount of time (e.g., 30 minutes, 5 minutes, 10 seconds, 30 seconds, 1hour, 2 hours, etc.). Accordingly, the device may include an non-activetimer to determine the amount of user non-activity. Additionally, themessage may provide a suggestion as to a type of activity the usershould perform to counter any risks introduced by the inactivity. Forexample, the system may suggest that the user walk 1 hour at a 10 minutemile pace. When the user has counteracted or accounted for the risks ornegative effects of the detected amount of inactivity time, acelebratory message or other indication may be provided.

Warnings, point deductions and/or other notifications may be provided ifa user returns to a sedentary or a non-active mode within a specifiedamount of time of exiting sedentary or a non-active mode. For example,the user may exercise or exhibit a sufficient level of activity to exitthe sedentary or a non-active mode for a period of 10 minutes. However,the system or device may require at least 30 minutes of activity toavoid additional warnings for a period of time such as 1 hour, 2 hours,3 hours, etc. For example, the warnings may indicate that the user didnot exhibit activity for a sufficient amount of time or a sufficientlevel of activity or a combination thereof. Additionally, multiplesedentary periods within short amounts of time (e.g., a threshold amountof time) may require higher or additional levels of activity tocounteract potential sedentary effects including health risks and thelike. In a particular example, the user may be required to perform ahigher level of activity to halt point deduction.

The device or other system may further advise a user as to an amount ofnon-active time allowed before negative health effects may occur. In oneexample, the device or system may include a countdown indicating aremaining amount of allowable non-active time before potential healthrisks may begin taking effect. An amount of permissible non-active timemay be earned or accumulated based on an amount of activity performed.Accordingly, the device may also provide suggestions or recommendationsas to a type and/or duration of activity that may be performed to earn aspecified amount of non-active time (e.g., 1 hour of TV watching).Different types of non-active or sedentary activities may requiredifferent types or amounts of activity. For example, 1 hour of recliningmay require more strenuous or longer exercise than 1 hour of sitting. Inanother example, 1 hour of sitting while knitting may require lessstrenuous or a lower amount of exercise or activity than 1 hour ofsitting while watching television. According to one or morearrangements, recommendations may be generated based on empirical dataand/or predefined programming and data tables specifying a type and/orduration of activity and a corresponding amount of permissiblenon-activity.

The device or activity tracking system may further recommend activitiesbased on historical records. For instance, the device or tracking systemmay determine activity performed by the user in the past and generaterecommendations based on those types of activities. Additionally oralternatively, the device or tracking system may generaterecommendations for specific workouts performed by the user in the past.For example, a user may need to perform 500 calories worth of activityto counteract 2 hours of TV watching. In such a case, the system mayrecommend a particular workout performed by the user in the past inwhich the user burned 500 calories. Combinations of historical activitytypes and specific historical workouts may be used to generaterecommendations. In one example, the system may recommend one of twoworkouts that the user has performed in the past based on a type ofworkout that the user appears to prefer. The preference may bedetermined based on a number of times the user has performed each typeof workout. A workout or activity type may also be recommended based onlocation and time. For example, if a user previously performs aparticular type of activity or a particular workout routine at the samelocation and/or at the same time, the system may recommend that type ofactivity or workout routine. Other recommendations algorithms andfactors may be used.

As disclosed herein, the spine member 24 provides a chassis member thatsupports various components of the device 10. It is understood that thespine member 24 could be eliminated or combined with other components inother exemplary embodiments. A flexible PCB member could be providedhaving localized stiffening members. Additional components are attachedto the flexible PCB member. In this configuration, the spine member 24is not used. In constructing the device, an inner portion of the outerencasement member may be formed in an injection molding process and thenthe flexible PCB member is attached to this inner portion. The remainingouter portion of the outer encasement member is formed over the PCBmember.

In another embodiment, the device 10 may have a housing that issubstantially rounded. The housing may have a substantially circularcross-section and have a tubular configuration. The housing has similarfeatures as described above wherein the display and/or indicator systemis viewable through an outer encasement member that is tubular. Ends ofthe housing may employ cooperating members in an interference fit andinclude a data transfer member at one of the device. The data transfermember may take any of the forms previously described such as a microUSB member and may include a further adapter member to a full USBconnector. The device may include an integrated PCB member and LED/lightpipe assembly as well as a micro piezoelectric accelerometer that may bealso three-axis accelerometer. The accelerometer senses activity and theLED/light pipe assembly may be illuminated based on the sensed activity.Other features described above may be incorporated into this embodimentas desired.

The device may also incorporate various other features and alternativestructures. The display and/or indicator system may utilizeelectrophoretic ink devices. The display and/or indicator system mayalso take other forms such as an electro luminescent/phosphorescentribbon display, electro-chromic ink devices, electrowetting devices, orfiber optic displays. The accelerometers can take various formsincluding piezoelectric accelerometers or nano accelerometers. Thebattery employed could be any lithium ion battery cells and may have atubular configuration as well as other types of power supplies. Thehousing may include a plurality of interconnected links that arestretchable wherein certain links may include a display segment thereon.The links may be interconnected via an elastic cord having conductivetraces. The housing may also utilized dual capacitive touch sensors toactivate the display and/or the indicator system. The display mayfurther take the form of a touch-activated screen. The housing may alsoincorporate a display utilizing an electro-chromatic polymer having aplurality of leads or pipes. Each pipe is wired to an electrode andencapsulates an electro-chromatic polymer than changes color when achange of current is applied from the controller. The housing mayfurther take the form of an elongated strap that can be coiled up toadjust the circumference of the device.

The device 10 provides numerous benefits. The device has a compactdesign that is easily wearable by a user at all times. The deviceincorporates a reliable data transfer device in the form of the USBconnector to easily transfer data to and from the device. The device isfurther capable of interacting with other mobile devices and remotesites provide enhanced user experiences that increase activity andperformance of the user. The device is also capable of tracking multipletypes of activity and can further track a user's activity for anextended period of a day as well as for a complete 24 hour period fromday to day. The indicator system provides an easy and enhancedmethodology to communicate activity information to the user. Messagescommunicated via the device 10 provide motivation to the user toincrease total activity and provide a healthier lifestyle. The devicestructure also provides significant benefits. The housing has flexiblezones allowing for ease of removing from and placing on a user's wristwhile providing sufficient rigidity to protect the components supportedby the housing. The spacer member allows for easy size adjustments.

FIGS. 145-178 illustrate different views of additional embodiments ofthe wearable device assembly 10 of the present invention. It isunderstood that any of the features of the additional embodiments can beutilized in combination with any of the features described above. It isfurther understood that similar structures will be designated withidentical or similar reference numerals. As discussed, the wearabledevice assembly 10 generally includes the housing 12, the controller 14,the input button 16, the display 18, and the indicator system 20. Thecontroller 14 has and/or is operably connected to various associatedcomponents including power supplies, sensors and associated circuitry.Also similar to prior embodiments, the housing 12 is in the form of awearable band such as a wristband and generally includes the inner spinemember 22 (FIGS. 6-9) having compartments for power supplies, the outerencasement member 24, and the fastening mechanism 26 or latch member 26.In certain exemplary embodiments, the housing 12 may have one or morespacer members 28 to adjust the size of the device 10 to be discussed ingreater detail below.

As previously described and shown, the inner spine member 22 is a memberhaving substantially rigid portions and certain flexible portions orzones. The inner spine member 22 shown in FIGS. 145-150 is substantiallythe same as the spine member 22 shown in FIGS. 7-9 above, butincorporates additional structures in the form of plug members toenhance the overall structure of the wearable device assembly 10 asdescribed herein. The spine member 22 has the general curvilinearconfiguration and has the outer surface 30 and the inner surface 32. Thespine member 22 has the intermediate portion 34 that extends to thefirst distal end 36 and the second distal end 38. The intermediateportion 34 has a central portion or central segment 40 as well as afirst segment 42 and a second segment 44. The intermediate portion 34further has the first flexible zone 46 or member or portion thatconnects one end of the central portion 40 to the first segment 42, andhas the second flexible zone 48 or member or portion that connects theother end of the central portion 40 to the second segment 44. Theflexible zones 46,48 provide for more easy flexing of the spine member22 at these zones and also the overall device while the first segment 42and second segment 44, and central portion 40, are considered rigidzones or substantially rigid zones. In an exemplary embodiment, theflexible zones 46,48 may be considered flexible hinge zones and arecurved segments in a generally concave shape. Thus, the flexible zoneshave a central portion or base portion with a pair of members extendingaway from the base portion, and therefore define an inwardly curvedportion, thus having a concave upper facing surface 500. The curvedsegments have a thinned out thickness at the base or central portion ofthe concave configuration to enhance the flexible characteristics of theflexible zones 46,48. Thus, the spine member 22 has a general thicknessor first thickness along its length (e.g., the rigid central portion andrigid first and second segments) while the flexible zones have a lesser,second thickness to assist in the flexible characteristics of the spinemember 22 and overall housing 12. In particular, the base portion of theflexible zone has a lesser thickness than the rigid central portion andfirst and second rigid segments. The first flexible portion defines afirst recessed area A and the second flexible zone defines a secondrecessed area A. The generally concave-shaped, inwardly curved flexiblezones 46,48 define the area A above the base portion and pair ofmembers, which is a U-shaped area in an exemplary embodiment. The areasA have a depth defined between an inner surface at the base extending upto a curvilinear arc AR defined by the outer surfaces of the adjacentcentral segment and first and second segments.

As also discussed, the flexible printed circuit board (PCB member) 140(FIG. 1460 is connected to the inner spine member 22. To this end, thePCB member 140 is in surface-to-surface engagement with the inner spinemember 22 including along the first flexible zone 46 and the secondflexible zone 48. The PCB member 140 has the flex regions 140 b thatcorrespond in position to the flexible zones 46,48 of the spine member22. As previously described, the PCB member 140 is wrapped around andmounted to the spine member 22. Fasteners may be used to fixedly attachthe PCB member to the spine member 22 including mechanical fasteners andadhesives. It is understood that the central region 140 a of the PCBmember corresponds to the central portion 34 of the spine member 22 whenconnected. The PCB member 140 generally follows the contours of thespine member 22 including the contours of the flexible zones 46,48.Thus, the flex regions 140 b are positioned at the flexible zones 46,48of the spine member 22 and are in general surface-to-surface engagement.Openings 516 are provided through the PCB member 140 at the flex regions140 b to expose portions of the spine member at the flexible zones46,48. It is further noted that the indicator system 20 is operablyconnected to the PCB member 140 as shown in FIG. 146f and extends fromthe main portion of the member 140. The indicator system 20 is foldedinto the edge of the spine member 22 as shown in the figures.

As shown in FIGS. 146-150, the spine member 22 utilizes plug members atthe flexible zones 46,48 and specifically includes a first plug member502 and a second plug member 504. The first plug member 502 and thesecond plug member 504 have a generally convex lower outer surface 506and a generally smooth upper surface 508. The convex surface 506 isshaped and dimensioned to follow the contours of the base and pair ofinwardly curved walls and concave surface 500 of the flexible zones46,48 of the spine member 22. The first plug member 502 and the secondplug member 504 each have a height that generally corresponds to theheight of the area A defined by the flexible zones 46,48. It isunderstood that one or both of the plug members 502,504 may have anopening therein to receive an additional fastener. The plug members502,504 can be formed from a variety of materials. In one exemplaryembodiment, the plug members 502,504 are formed from polypropylene.

As shown in FIGS. 146-150, the first plug member 502 is positionedproximate the first flexible zone 46 and a second plug member 504 ispositioned proximate the second flexible zone 48. In particular, thefirst plug member 502 is adhered via an adhesive to the PCB member 140at the first flexible zone 46. Openings 516 in the flex regions 140 b ofthe PCB member 140 allow for some direct adherence of the plug member tothe spine member 22. In an exemplary embodiment, the adhesive may be aVHB adhesive tape member 514 (FIG. 146d ) such as provided by the 3MCompany. The tape may have a substrate having the adhesive on both sidesof the substrate. The convex surface 506 of the first plug member 502confronts the flex regions 140 b of the PCB member 140 and the concavesurface 500 of the first flexible zone 46 and is in surface-to-surfaceengagement, thus connecting the plug member 502 to the PCB member 140and the spine member 22. The first plug member 502 generally occupiesthe area A defined by the first flexible zone 46. As the height of thefirst plug member 502 generally corresponds to the height of the area Aof the first flexible zone 46, the upper surface 508 of the first plugmember 502 is positioned generally in line with and proximate thecurvilinear arc AR defined by the outer surface of the spine member 22.Similarly, the second plug member 504 is adhered via the adhesive member514 to the PCB member 140 at the second flexible zone 48. The convexsurface 506 of the second plug member 504 confronts the flex regions 140b of the PCB member 140 and the concave surface 500 of the secondflexible zone 48 and is in surface-to-surface engagement, thusconnecting the plug member 502 to the PCB member 140 and the spinemember 22. The second plug member 502 generally occupies the area Adefined by the second flexible zone 48. As the height of the second plugmember 504 generally corresponds to the height of the area A of thesecond flexible zone 48, the upper surface 508 of the second plug member504 is positioned generally in line with and proximate the curvilineararc AR defined by the outer surface of the spine member 22.

The first plug member 502 and the second plug member 504 assist inconnecting the PCB member 140 to the spine member 22. As there areopenings 516 through the PCB member 140 at the flex zones 140 b, thereis some direct contact with the adhesive between the plug members502,504, the PCB member 140 and the spine member 22. Thus, the flexiblezones 46,48, adhesive member 514 and plug members 502,504 are invertical stacked arrangement as shown in FIGS. 148-150). Thepolypropylene plug members 502,504 still allow sufficient overallflexibility of the wearable device assembly 10. In one or more examples,the flexibility of the zones proximate to the plug members 502,504 maybe at or above one or more predefined flex values or thresholds toprovide the overall flexibility. Moreover, plug members 502,504 may eachhave different flexibilities. Still further, in one or morearrangements, the flexible zones 46,48 and plug member 502,504 may havedifferent shapes that correspond to one another.

As can be appreciated from FIG. 150, the plug members 502,504 assist inenhancing the over-molding of the outer polymeric encasement member ofthe housing. As the encasement member 24 is molded over the assembly,the plug members 502,504 assist in keeping the PCB member 140 downagainst the spine member 22, thus minimizing the chances for the PCBmember 140 to lift off of the spine member 22. The plug members 502,504,therefore, assist in preventing the PCB member 140 from straighteningout across the flexible zones 46,48. In addition, as the plug members502,504 occupy the area defined by the flexible zones 46,48, lesspolymeric encasement material is required at the flexible zones 46,48.Accordingly, the thickness t (FIG. 150) of the elastomer member 24 atthe first flexible portion 46 is approximately the same as the thicknesst of the elastomer member 24 adjacent the first flexible portion 46.Similarly, the thickness t of the elastomer member 24 at the secondflexible portion 48 is approximately the same as the thickness t of theelastomer member 24 adjacent the second flexible portion 48. This helpsprevent any potential sinking or sagging of the outer encasementmaterial at these areas. This provides an enhanced encasement member 24of the housing 12 as any potential surface irregularities are minimized.While in an exemplary embodiment the plug members 502,504 are adheredvia an adhesive, the plug members 502,504 may also be adhered usingmechanical fasteners including one or more threaded screw fasteners.Thus, threaded fasteners can also be used to connect the plug members502,504 to the PCB member 140 and spine member 22. The plug members502,504 could also be heat-staked if desired. An alternativereinforcement member may take the form of a clamp member such as shownin FIG. 146e . The clamp member 518 may be fastened to the PCB member140 and spine member 22 with a screw 519. Clamp members 518 may bepositioned on each side of the flexible portions 46,48 and could also beused in conjunction with the plug members 502,504. The clamp members 518also assist in keeping the PCB member 140 down on the spine member 22.

FIGS. 151-154 disclose an alternative embodiment of the first projectionmember 90 in the form of the USB connector 94 that can be used in thewearable device assembly 10. In this embodiment, the rigid body and theleads of the connector 94 have a generally flush configuration asdescribed in greater detail below. As shown in FIGS. 152-153, the USBconnector 94 has a plurality of leads 520. Each lead 520 has a basemember 522 that is subjected to a mechanical coining fabricationprocess. The coining process compresses the leads thereby movingmaterial to form a peripheral support wall 524 defining a peripheralsurface 526. The movement of material from the coining process furtherdefines a raised planar platform 528 positioned inwardly from theperipheral support wall 524. With such configuration, the leads 520 arepositioned in a mold assembly wherein mold members can be positioned tolocations corresponding to the raised planar platforms 528 and beneaththe leads 520. Material can then be injected into the mold assembly toform the rigid body 530. Because of the configuration of the moldmembers, as shown in FIGS. 151 and 154, the rigid body 530 is generallyflush with the raised planar platforms 528. Thus, the raised planarplatforms 528 are generally at the same level as the top surface of thebody 530. Such configuration provides enhanced operable connection withthe USB connector 94 is inserted into a USB receptacle such as thecomputer shown in FIG. 44. Other mechanical fabrication techniques canalso be used on the leads 520 to move material as desired includingother forging processes and molding operations. As further shown in FIG.155, the rigid body 530 can be formed with a beveled edge or angledsurface 532. In this exemplary embodiment, the beveled edge 532 ispositioned on the underside surface having the recess therein. Thebeveled edge 532 is generally adjacent to the recess as shown in FIG.155. The beveled edge 532 provides a lead-in structure to allow easierand smoother insertion of the USB connector 94 into the second receivermember 92.

FIGS. 156-173 disclose additional embodiments and features of thefastening mechanism 26 and spacer member 28 of the wearable deviceassembly 10 of FIG. 1.

As previously discussed, the fastening mechanism 26 or latch member 26generally includes a first projection member 90 and a second receivermember 92. The first projection member 90 is positioned proximate thefirst end of the housing 12, and the second receiver member 92 ispositioned proximate the second end of the housing 12. It is understoodthat the members 90,92 could be placed on opposite ends of the housing12 if desired. The first projection member 90 incorporates aninput/output member 94 for data transfer and in an exemplary embodiment,takes the form of the USB connector 94. It is understood that the USBconnector 94 as described herein forms part of the alternative fasteningmechanisms 26 described herein.

FIGS. 156-160 disclose a second receiver member 92 and a spacer member28 having alternative connection structures. Similar structures will bedesignated with like reference numerals. It is understood that thesecond receiver member 92 could be directly connected to one end of thehousing 12, but that the spacer member 28 can be utilized to expand thecircumferential size of the device 10 so that device size can be varied.The second receiver member 92 defines the opening 104 therein andsupports a pivoting member 106 that cooperates with the first projectionmember 90 as described herein. As shown in FIGS. 156-159, the secondreceiver member 92 has a central prong member 570 at an opposite endfrom the opening 104. The central prong member 570 is a single memberand is positioned generally at a mid-portion of the second receivermember 92. The prong member 570 has a first lateral projection 572 and asecond lateral projection 574 extending from the prong member 570. Thelateral projections 572,574 define engagement surfaces 576 (FIG. 158).

As further shown in FIG. 160, the spacer member 28 has the body 130having one end having a central opening 580 generally dimensioned toreceive the central prong member 570. The central opening 580 has afirst peripheral segment 582 and a second peripheral segment 584.Engagement surfaces are defined at backside surfaces adjacent to thecentral opening 580. The other end of the body 130 has a central prongmember 586 (FIG. 156b ) having a first lateral projection 588 and asecond lateral projection 589 similar to the central prong member 570 onthe second receiver member 92.

It is further understood that in this embodiment, the end of the housing12 will have an opening similar to the central opening 580 in the spacermember 28. Thus, when using a spacer member 28, the second receivermember 92 is rotated (see arrows in FIG. 156 b) about an axis extendingfrom the central prong member 570 to a first position wherein the prongmember 570 is aligned with the central opening 580. In addition, thefirst lateral projection 572 is aligned with the first peripheralsegment 582 and the second lateral projection 574 is aligned with thesecond peripheral segment 584. The prong member 570 is fully insertedinto the central opening 580 wherein the second receiver member 92 isrotated back to a second position to align the outer surfaces of thesecond receiver member 92 with the outer surfaces of the spacer member28. The engagement surfaces 576 of the lateral projections 572,574 thenengage the backside engagement surfaces of the spacer member 28 toconnect the second receiver member 92 to the spacer member 28.Similarly, the central prong member 586 on the other end of the spacermember 28 is rotated about an axis extending from the prong member 586and is inserted into a corresponding opening on the end of the housing12 and rotated back to connect the spacer member 28 and second receivermember 92 to the end of the housing 12. Thus, a rotatable cooperatingconnection mechanism is provided in the alternative embodiment shown inFIGS. 156-160. It is understood that the first projection member 90 canbe inserted into the opening 104 of the second receiver member 92 aspreviously described herein.

FIGS. 161-165 disclose another alternative latching mechanism 26 alongwith a spacer member 28. It is understood that FIGS. 161-165 disclose asecond receiver member 92 that will cooperate with the first projectionmember 90 having a USB connector 94 in an exemplary embodiment. As such,the second receiver member 92 will have the opening 104 to receive theUSB connector 94. The other end of the second receiver member has a pairof posts 590 extending therefrom. Each post 590 has an inclined camsurface 592 and a slot 594 defined along a length of the post 590. Asfurther shown in FIGS. 164-165, one end of the spacer member 28 has apair of openings 596 to receive the posts 590 of the second receivermember 92. It is understood that a plate member 598 on the spacer member28 (FIG. 161) is removed in FIGS. 164-165 to more easily view theadditional components. The spacer member 28 further internally supportsa pair of fingers 600. Each finger 600 has a distal end 602 and agenerally spherical ball-shaped proximal end 604. The fingers 600 arebiased outwardly by a central base member 606. The central base member606 has a pair of inclined surfaces 608 and a slot 610 that receives abiasing spring 612 that is supported by a floor 614 of the spacer member28. The spring 612 biases the base member 606 upwards wherein theinclined surfaces 608 act against the proximal ends 604 of the fingers600 to bias the fingers 600 outwardly. It is understood that an oppositeend of the spacer member 28 will have a pair of posts similar to theposts 590 on the second receiver member 92 to achieve the daisy chainconnecting arrangements as described in the various embodiments herein.Accordingly, the end of the housing 12 will have structures similar tothe internal biased fingers just described regarding the spacer member28.

In operation and as can be appreciated from FIGS. 161-165, it isunderstood that the one end of the spacer member 28 is connected to theone end of the housing 12. The posts 590 on the second receiver member92 are inserted into the openings 596 of the spacer member 28. Theinclined cam surfaces 592 on the posts 590 push the fingers 600 inwardlywherein the ball-shaped proximal ends 604 move along the inclinedsurfaces 608 of the base member 606 compressing the biasing spring 612.Upon further insertion, the fingers 600 are biased by the spring 612into the slots 594 in the posts 590 wherein the second receiver member92 is connected to the spacer member 28. The opening of the secondreceiver member 92 can receive the USB connector 94 of the firstprojection member 90 to connect the ends of the device 10. As discussed,it is understood that the spacer member 28 has similar posts that areconnected to the end of the housing 12 having similar biased fingers. Ifa spacer member 28 was not used, the posts 590 on the second receivermember 92 are inserted directly into the end of the housing 12 whereinsimilar connection structures are present.

FIGS. 166-169 disclose another alternative fastening mechanism 26. Thefastening mechanism 26 utilizes a first projection member 90 and asecond receiver member 92 that cooperate with ends of the housing 12.The first projection member 90 may include a USB connector 94 havingleads as described herein with the appropriate operable connections. Onone end of the rigid body of the USB connector 94, a slot 620 is definedtherein. The slot 620 has a first segment 622 and a second segment 624generally transverse to the first segment 622. The second receivermember 92 has an internal opening 626 and a depending projection 628therein. The depending projection 628 has a first section 630 and asecond section 632 that is generally transverse to the first section630. When the first projection member 90 is inserted into the secondreceiver member 92, the projection 628 is received in the slot 620. Inparticular, the first segment 622 receives the first section 630 and thesecond segment 624 receives the second section 632. The engagementsurface of the first segment 622 cooperates with the engagement surfaceon the first section 630 of the projection 628 to connect the members90,92. To disconnect, a user squeezes the second receiver member 92 toprovide a force F laterally inwardly as shown by the arrows in FIG. 169.In response, the second receiver member 92 expands upwardly anddownwardly as shown by the arrows wherein the projection 628 is removedfrom the slot 620 wherein the first projection member 90 may be removedfrom the second receiver member 92.

FIGS. 170-173 disclose another alternative fastening mechanism 26. Thefirst projection member 90 may be similar to prior embodiments andincorporate a body and the USB connector 94 having leads, otherstructures and the necessary operable connections as described herein.The connector 94 has a pair of notches 638 in lateral sides of theconnector 94. The second receiver member 92 has a support body 641having a central opening 640 (FIG. 173) to receive the USB connector 94.The second receiver member 92 also supports a pair of resilientlyflexible fingers 642. Each finger 642 has a first segment 644 and asecond segment 646 connected together at an end 648. One end of thefirst segment 644 is connected to the support body 641 and anintermediate portion 650 of the first segment 644 contacts the supportbody 641. A distal end of the second segment 646 has a latch member 652.It is understood that a sheath can be provided over the second receivermember 92 or the outer encasement member 24 of the housing 12 can bemolded over the second receiver member 92 in an exemplary embodiment. Ina connected position such as shown in FIG. 171, the first projectionmember 90 is inserted through the opening 640 and the latch members 652are received in the notches 638. To disengage, the fingers 642 aresqueezed through the housing 12 at the ends 648 and in the direction ofthe arrows shown in FIG. 171. This pivots the second segment 646 of thefingers 642 outwardly wherein the latch members 652 are removed from thenotches 638. This allows the first projection member 90 to be removedfrom the second receiver member 92. Similarly when reconnecting, the USBconnector 94 is inserted into the opening 640 wherein the secondsegments 646 are deflected until the latch members 652 are received inthe notches 638 as can be appreciated from FIG. 171.

FIGS. 174-178 disclose an alternative embodiment of the input button 16that can be used in the wearable device assembly 10 of the presentinvention. As shown in FIG. 176-178, the input button 16 has a basemember 550 supporting a contact 551. The button 16 further has anactivation post 552 as well as a flexible cap member 554. The activationpost member 552 is supported by a resiliently flexible serpentine member553 that is connected to the base member 550. The base member 550 isgenerally supported in a well located in the spine member 22 and isoperably connected to the PCB member 140 via a pair of leads 555. Theactivation post 552 is connected onto the base member 550 and positionedover the contact 551. In addition, the activation post 552 has agenerally cylindrical configuration and is received through acorresponding circular aperture formed in the PCB member 140. As shownin FIG. 178, the flexible cap member 554 is positioned over the post 552and is supported on the PCB member 140. The flexible cap member 554 mayhave similar engagement surfaces as described above that are used whenforming the outer encasement member 24 of the housing 12. Upondepression of the flexible cap member 554, the activation post 552 isdeflected downward to engage the contact 551 to provide an input to thedevice 10.

It is further understood that the wearable device assembly 10 describedherein can include additional modifications and features. For example,while the inner spine member is a polymeric member in one exemplaryembodiment, the spine member may also be made from spring steel or othermetallic materials having sufficient resilient flexibility. In anotherexemplary embodiment, the wearable device assembly 10 may utilize asingle battery. In this exemplary embodiment, the spine member may havea single battery compartment. In such a configuration, any inner supportmember such as the spine member will have additional space and locationsto support additional componentry such as additional sensors and largerdisplays and/or indicator systems. Such configuration further providesincrease flexing options for the wearable device assembly 10. In anotheralternative embodiment, a single battery can be supported at a centrallocation of the device such as at a central location of the inner spinemember underneath the display. Such configuration can also providesimilar benefits regarding flexibility and space for additionalcomponentry as described above. The outer encasement member of thehousing may also include materials having glow-in-the-darkcharacteristics which can enhance the display abilities of the device10. The device 10 can also employ a display and/or indicator systemutilizing side-firing LED elements. The use of light pipes could also beused in such designs. Such side-firing LED designs could be used withLEDs positioned at a central location of the device 10. In furtherexemplary embodiments, flexible battery leads may be utilized. Forexample, the battery may have a pair of leads each having a lengthextending between opposite ends. One end may be solder-connected to thebattery and the other end may be solder-connected to the PCB member.When the battery is positioned in the battery compartment, the length ofthe battery lead may be folded upon itself, and then the battery closuremember is connected over the battery. The batteries may also besubjected to various treatments such as heat treatments to enhanceperformance. The device 10 utilizes curved batteries and the curvatureof the batteries can also be varied as desired. Other latch mechanismarrangements may also be utilized such as a hingedly attached member onthe second receiver member pivotally attached to the first projectionmember. Latch mechanisms using a rotating pawl activated by a pushbutton are also possible. As previously discussed, adhesion promoterscan be utilized with the device when forming the outer encasement memberover the spine member and PCB member to minimize any chances for airgaps to form between the inner components of the device and the innersurfaces of the outer encasement member. Eliminating any air gapsprovides enhanced lighting of the display and indicator system throughthe housing 12, particularly enhancing the display of colored lightthrough the housing 12. It is understood that the various features andstructures of the various embodiments may be used in combination to formthe wearable device assembly 10 of the present invention as well asutilize and incorporate the various user interface and experiencefeatures described herein.

Data Synchronization

As described herein, data recorded by an athletic activity monitoringdevice, such as device 10 and/or a mobile communication device (e.g., asmartphone), may be synchronized to one or more other systems (remote orlocal). In one example, the synchronization destination system maycomprise a remote network site and system configured to track physicalactivity information for a community of users. Synchronization of datawith an activity monitoring system may require the user to connect tothe activity monitoring system and interact with one or more componentsthereof such as user interfaces, options, software modules and the likeor combinations thereof. The user interfaces may be configured to conveyinformation including product recommendations, informational articles,activity statistics, social networking data, user messages and the like.

According to one aspect, a game or other function of an activitymonitoring device may allow a user to compete with another user based onvarious activity metrics. The game or other function may allow the userto specify a particular activity type, device type specific (e.g.,capabilities of the device, device model, device manufacturer, devicecomponents) and the. Accordingly, activity data that does not match thespecified activity type and/or device type might not be registered forthe game or other function. In a particular example, a first portion ofa user's activity data stored in the activity monitoring device mayinclude data corresponding to the specified activity type and/or devicetype and a second portion that does not. Accordingly, only the firstportion of the user's activity data may count toward a challenge,competition or game between the user and at least one other user. Insome examples, the creator of a competition may specify an amount ofactivity required to win the competition. The amount of activity may beexpressed in different metrics, if desired. Accordingly, the user maymanually and individually specify an amount of activity required to winin each of the different metrics. In some examples, the amount ofactivity in each of the different metrics might not correspond to adirect conversion, while in other examples, the amounts may be directconversions.

FIG. 179 illustrates an example activity monitoring game in which two ormore users may compete to earn a specified amount of activity metric. Asnoted above, the game may be activity type and/or device type specific.Additionally, activity data might not count toward the game until theuser synchronizes his or her data with an activity monitoring system. Assuch, even if the user records 100 miles on his or her activitymonitoring device, the 100 miles will not count toward the game or othercompetition unless the data is synchronized to an activity monitoringsystem (e.g., a remote network site). Synchronization may include thetransmission and/or storage of the data at the activity monitoringsystem. In some examples, a confirmation may be required to reflect thatthe data has been registered toward the game or challenge.

FIG. 180A illustrates an example synchronization interface for anactivity challenge.

FIGS. 180B and 180C illustrate examples notification messages that maybe provided to a user depending on a current challenge status. Forexample, if a user is falling behind, the user may be provided with amotivation message, as shown in FIG. 180B. FIG. 180C illustrates anexample post-synchronization game status message. After data has beensynchronized, the display may reflect a comparison between thecompetitor's registered activity.

FIGS. 181A-181F illustrate example synchronization interfaces. Theinterfaces may reflect whether each user has or has not synchronizedtheir data. A final score or winner might only be determined once allusers have synchronized their data (e.g., at or after the completion ofthe game).

In one or more arrangements, an objective of competition or challengemay be to accumulate a certain amount of activity in the shortest time.Such a challenge may encourage a user to synchronize his or her data asfrequently as possible. Accordingly, this objective in conjunction withthe requirement to synchronize the data for the data to count toward theobjective, may allow an activity monitoring system to maximize userinteractivity. For example, the activity monitoring system may beprovided with more opportunities to convey information (such as productrecommendations, reminders, advertisements, fitness advice, etc.) to theuser and/or to receive information from the user. The increasedfrequency of receiving or transmitting data may allow the system to getcloser to real-time accuracy of activity data among its community ofusers. A creator of a game may, in some arrangements, specifycharacteristics of users that are allowed to participate in thechallenge. These characteristics may include location, height, weight,gender, age, level of athleticism (e.g., beginner, novice, intermediate,expert; low, medium, high, etc.) and the like and/or combinationsthereof.

In yet other examples, a competition or activity monitoring system mayrequire participants to synchronize data at a specified frequency (e.g.,once every 30 minutes, twice every 15 minutes, once every hour, etc.)and/or at specified times. If the user does not synchronize the dataaccordingly the specified schedule, the user might only be permitted tosynchronize data recorded for a next window of time. For example, if auser does not synchronize his or her data during a first 30 minutewindow for a challenge requiring synchronization every 30 minutes, theunsynchronized data (e.g., activity performed) recorded by the user forthat first 30 minute window might not count toward the challenge. Inanother example, if a user does not synchronize his or her data atspecified times (or within an amount of time of the specified times),the user's unsynchronized data prior to and up until the specified timemight not count toward the challenge. Various other arrangements may bedefined for a challenge.

CONCLUSION

While the invention has been described with respect to specific examplesincluding presently preferred modes of carrying out the invention, thoseskilled in the art will appreciate that there are numerous variationsand permutations of the above described systems and methods. Forexample, various aspects of the invention may be used in differentcombinations and various different subcombinations of aspects of theinvention may be used together in a single system or method withoutdeparting from the invention. In one example, software and applicationsdescribed herein may be embodied as computer readable instructionsstored in computer readable media. Also, various elements, components,and/or steps described above may be changed, changed in order, omitted,and/or additional elements, components, and/or steps may be addedwithout departing from this invention. Thus, the invention should beconstrued broadly as set forth in the appended claims.

What is claimed is:
 1. A non-transitory computer readable medium storinginstructions that, when executed, cause an apparatus to: detect, fromdata received from an accelerometer sensor integrated into theapparatus, activity performed by a user for an activity competition;determine that the activity performed by the user has been registeredtoward the activity competition only upon determining that activity datacorresponding to the detected activity has been synchronized through anetwork system with at least one other apparatus; receive furtheractivity data; determine a required synchronization frequency; triggersynchronization of the further activity data by transitioning theapparatus from a sleep state to an active state; and determine whethersynchronization of the further activity data was requested in accordancewith the required synchronization frequency.
 2. The non-transitorycomputer readable medium of claim 1, wherein the transitioning theapparatus from the sleep state to the active state is initiated using auser interface of the apparatus by pulling and releasing the userinterface using a touch input.
 3. The non-transitory computer readablemedium of claim 1, wherein the synchronization frequency is specified bythe activity competition.
 4. The non-transitory computer readable mediumof claim 1, wherein the network system is located remotely from theapparatus.
 5. The non-transitory computer readable medium of claim 1,wherein detecting activity performed by the user includes: receivingdata corresponding to the activity performed by the user; determining atype of activity specified for the competition; and extracting only datacorresponding to the determined type of activity as the activity data tobe synchronized.
 6. The non-transitory computer readable medium of claim1, wherein detecting activity performed by the user includes: receivingdata corresponding to the activity performed by the user; determining atype of device specified for the competition; and extracting only datacorresponding to the determined type of device as the activity data tobe synchronized.
 7. The non-transitory computer readable medium of claim1, wherein the instructions, when executed, further cause the apparatusto: connecting to the at least one other apparatus through a wirelessconnection; and transmitting the activity data to the at least one otherapparatus.
 8. The non-transitory computer readable medium of claim 1,wherein determining that the activity data corresponding to the detectedactivity has been synchronized with the at least one other apparatusincludes receiving a synchronization confirmation from the at least oneother apparatus.
 9. The non-transitory computer readable medium of claim1, wherein the instructions, when executed, further cause the apparatusto: determine further activity data; determine a requiredsynchronization frequency specified by the activity competition; andsynchronize the further activity data with the at least one otherapparatus based on the required synchronization frequency.
 10. Thenon-transitory computer readable medium of claim 7, whereinsynchronizing the further activity data include receiving informationfrom the at least one other apparatus.
 11. The non-transitory computerreadable medium of claim 1, where in response to determining that thesynchronization of the further activity data was not requested inaccordance with the required synchronization frequency, preventing thefurther activity data from being synchronized with the at least oneother apparatus.
 12. A method comprising: detecting, from data receivedfrom an accelerometer sensor integrated into an apparatus, activityperformed by a user for an activity competition; determining that theactivity performed by the user has been registered toward the activitycompetition only upon determining that activity data corresponding tothe detected activity has been synchronized through a network systemwith at least one other apparatus; receive further activity data;determine a required synchronization frequency; trigger synchronizationof the further activity data by transitioning the apparatus from a sleepstate to an active state; and determine whether synchronization of thefurther activity data was requested in accordance with the requiredsynchronization frequency.
 13. The method of claim 12, wherein thetransitioning the apparatus from the sleep state to the active state isinitiated using a user interface of the apparatus by pulling andreleasing the user interface using a touch input.
 14. The method ofclaim 12, wherein the synchronization frequency is specified by theactivity competition.
 15. The method of claim 12, wherein the networksystem is located remotely from the apparatus.
 16. The method of claim12, wherein detecting activity performed by the user includes: receivingdata corresponding to the activity performed by the user; determining atype of activity specified for the competition; and extracting only datacorresponding to the determined type of activity as the activity data tobe synchronized.
 17. The method of claim 12, wherein detecting activityperformed by the user includes: receiving data corresponding to theactivity performed by the user; determining a type of device specifiedfor the competition; and extracting only data corresponding to thedetermined type of device as the activity data to be synchronized. 18.The method of claim 12, further comprising: connecting to the at leastone other apparatus through a wireless connection; and transmitting theactivity data to the at least one other apparatus.
 19. The method ofclaim 12, wherein determining that the activity data corresponding tothe detected activity has been synchronized with the at least one otherapparatus includes receiving a synchronization confirmation from the atleast one other apparatus.
 20. The method of claim 12, furthercomprising: in response to determining that the synchronization of thefurther activity data was not requested in accordance with the requiredsynchronization frequency, preventing the further activity data frombeing synchronized with the at least one other apparatus.